Known Issues: Business Process Manager Industry Packs V7.5 on Business Process Manager V7.5.1

Product readme


Abstract

This document describes the known issues with the usage of the IBM Business Process Manager Industry Packs Version 7.5 on IBM Business Process Manager Version 7.5.1.

Content

This document provides solutions to problems you might encounter (Known issues) while using IBM Business Process Manager Industry Packs Version 7.5 on Business Process Manager Version 7.5.1.

  • Problem: Import of IBM Business Process Manager Industry Packs V7.5 Process Applications through Installation scripts fails on Business Process Manager V7.5.1.


    Symptom: If you attempt to execute the V7.5 Installation scripts, they might see the following message in the <Industry Pack_ProcessAppinstall.log>:


    ************************************************
    Installing
    ************************************************
    Username is missing.
    Usage: installProcessAppPackage [options...] <package name> <username of the process server administrator> <user password>


    Solution: The workaround is to update the installer scripts for solution scenarios located under <industrypacks_install_location>/solution-scenarios/<solution scenario name>/scripts. The steps for updating are as follows:


    Update the "wleinstaller.bat" file in the scripts folder shown below:
    cd\
    cd /d %Lombardi_home%/tools/process-installer
    installProcessAppPackage"%ProcessAppPath%"/new-account-opening-install-pack.zip


    Update it as shown below:
    cd\
    cd /d %Lombardi_home%/tools/process-installer
    installProcessAppPackage"%ProcessAppPath%"/new-account-opening-install-pack.zip <username of the process server administrator> <user password>

  • Problem: For Business Process Manager Industry Packs V7.5 to function on Business Process Manager V7.5.1, the Toolkits and Process Applications need to be upgraded.


    Symptom: If you attempt to invoke a Toolkit/Process application (without upgrade) that contains Coaches in it, you might see the following exception:
    com.lombardisoftware.component.common.workflow.WorkflowProcessItemException: Could not find any parameter in HttpRequest matching a button on the Coach. Button pressed was ok
    at com.lombardisoftware.component.common.workflow.ExecutionJob.doJob(ExecutionJob.java:339)
    at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.doResumeWorkflowEngine(EJBWorkflowManagerBean.java:999)
    at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.resumeTask(EJBWorkflowManagerBean.java:280)
    at com.lombardisoftware.server.ejb.workflow.EJSRemoteStatefulEJBWorkflowManager_82478d70.resumeTask(Unknown Source)
    at com.lombardisoftware.server.ejb.workflow._EJBWorkflowManagerInterface_Stub.resumeTask(_EJBWorkflowManagerInterface_Stub.java:405)
    at com.lombardisoftware.component.common.workflow.EJBWorkflowManagerDelegateDefault.resumeTask(EJBWorkflowManagerDelegateDefault.java:117)
    at com.lombardisoftware.component.common.workflow.EJBWorkflowManagerDelegateWebSphere$3.run(EJBWorkflowManagerDelegateWebSphere.java:60)
    at java.security.AccessController.doPrivileged(AccessController.java:251)


    Solution: After importing any toolkit/process application of Business Process Manager Industry Packs V7.5 into Business Process Manager V7.5.1 Process Designer/Process Center, the “System data” toolkit needs to be upgraded and a new Snapshot should be taken before working on Industry Packs specific Toolkits/Process applications.


    The following steps enable you to upgrade the Toolkit and create a new snapshot:
    1. Import a toolkit into Process Designer.

    2. Click the Toolkit name. click Manage, and select the checkbox beside Allow users to update toolkit.

    3. Click Snapshots, click Open in Process Designer, and right-click the dependent toolkit. For example, System Data and click Upgrade dependency to V7.5.1.

    4. After the System Data toolkit is upgraded to V7.5.1, click Process Center.

    5. Click Create New Snapshot>>provide Snapshot Name

    The following steps enable you to upgrade the Process application and create a new snapshot:
    1. Import the process application into Process Designer.

    2. Click Open in Process Designer.

    3. Right-click Dependent toolkits and select Change/Upgrade the version of the dependency to latest. Perform this step for all the dependent toolkits.

    4. Click Process Center. Click Process application name and click Create New Snapshot.


    Note
    : For a Process application, make sure that all the dependent toolkits need to be upgraded for System data version and snapshot is taken.

  • Problem: For Business Process Manager Healthcare Pack V7.5 on Business Process Manager V7.5.1, while executing the Benefits Eligibility Process application/Solution Scenario, date values are not getting passed if you select Patient ID and submit default data.


    Symptom: For Business Process Manager Standard type execution,the date values are not passed and do not display values on the summary page. For Advanced type execution, the following exception is thrown:


    0000020a WebServiceExc E org.apache.axis2.jaxws.WebServiceExceptionLogger log A javax.xml.ws.WebServiceException throwable was caught. The detail message is: ataObject com.ibm.websphere.fabric.healthcare.payer.cbs.service.build270.Build270Impl.build(commonj.sdo.DataObject)] for component [{BenefitEligibilityModule}Build270]: caused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 10
    at com.ibm.wsspi.sca.jaxws.service.GenericJaxWsExportProvider.invoke(GenericJaxWsExportProvider.java:97)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.apache.axis2.jaxws.server.dispatcher.JavaDispatcher.invokeTargetOperation(JavaDispatcher.java:82)
    at org.apache.axis2.jaxws.server.dispatcher.ProviderDispatcher.invoke(ProviderDispatcher.java:136)
    at org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointController.java:111)
    at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:161)
    at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:189)
    at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
    at com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost(WASAxis2Servlet.java:1380)


    Solution: While executing the Benefits Eligibility Solution Scenario, in the “Submit Benefits Eligibility” page after selecting Patient ID, you must modify the date values. For example, modify the Date Of Birth and Date Of Service values and then click Submit on the page.


    Note: Modifying the date value to same date also works.

  • Problem: For Business Process Manager Healthcare Pack V7.5 on Business Process Manager V7.5.1, the execution of Claims Processing BPD fails.


    Symptom: It throws the following exception:


    com.lombardisoftware.component.common.workflow.WorkflowProcessItemException: Runtime error in script ("Process: 'Receive Notification Of Pended Claims' ProcessItem: 'Receive Notification of Pended Claims' Type: 'ITEM'" -1:-1).Internal Script error: com.lombardisoftware.core.TeamWorksRuntimeException: com.lombardisoftware.core.TeamWorksException: Type mismatch. Value "" must be instance of structured IBM Business Process Manager type. Java class found: java.lang.String
    at com.lombardisoftware.component.common.workflow.ExecutionJob.doJob(ExecutionJob.java:415)
    at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.doResumeWorkflowEngine(EJBWorkflowManagerBean.java:1003)
    at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.resumeTask(EJBWorkflowManagerBean.java:303)
    at com.lombardisoftware.server.ejb.workflow.EJSRemoteStatefulEJBWorkflowManager_82478d70.resumeTask(Unknown Source)
    at com.lombardisoftware.server.ejb.workflow._EJBWorkflowManagerInterface_Stub.resumeTask(_EJBWorkflowManagerInterface_Stub.java:347)
    at com.lombardisoftware.component.common.workflow.EJBWorkflowManagerDelegateDefault.resumeTask(EJBWorkflowManagerDelegateDefault.java:105)
    at com.lombardisoftware.component.common.workflow.EJBWorkflowManagerDelegateWebSphere$2.run(EJBWorkflowManagerDelegateWebSphere.java:52)
    at java.security.AccessController.doPrivileged(AccessController.java:251)


    Solution:
    1. Launch Process Designer and import the Claims Management toolkit.

    2. Make it writable. For example, click Claims Management>Manage and select the check box besides Allow users to update toolkit.

    3. Click Snapshot and click Open in Process Designer.

    4. Click User Interfaces and double click Receive Notification of Pended Claims to open.

    5. Open the Coach "Receive Notification of Pended Claims".
    6. Within the coach, in the "Subscriber Contact Information" section, complete the following steps:
      1. For label "<#= tw.resource.Common.city#>:" within the properties tab, on binding, select the mapping to tw.local.subscriberInfo.subscriberContactInfo.city.name

      2. For label "<#= tw.resource.Common.state#>:"within the properties tab, on binding select the mapping to tw.local.subscriberInfo.subscriberContactInfo.state.name

      3. For label "<#= tw.resource.Common.country#>:" within the properties tab, on binding select the mapping to tw.local.subscriberInfo.subscriberContactInfo.country.name

    7. Save the toolkit and execute.

  • Problem: For Business Process Manager Industry Packs V7.5 on Business Process Manager V7.5.1, while executing the Process application/Solution Scenario in Business Space, there is an error displayed in Task Information widget stating “403 BMWPX0006E: The URL you tried to access through the proxy is not allowed”.


    Symptom: You might see the following error while loading a task in Business Space:
    "403 BMWPX0006E: The URL you tried to access through the proxy is not allowed."


    Solution: Follow the steps mentioned in the Troubleshooting IBM Business Process Manager: "403 BMWPX0006E: The URL you tried to access through the proxy is not allowed" document:

  • Problem: For Business Process Manager Banking Pack V7.5 (New Account Opening) and Business Process Manager Telecom Pack (Order Handling) on IBM Business Process Manager V7.5.1, importing a Business Space file throws exception in the log files (systemout).


    Symptom: You might see the following exception in the log files:
    00000097 exception E com.ibm.ws.wim.adapter.urbridge.URBridge getSecNameFromUniqueID CWWIM4001E The '3958cdfe-fcb4-4b77-86cb-8dd9acfcb9f5' entity was not found.
    [10/4/11 1:40:29:052 CDT] 00000097 exception E com.ibm.ws.wim.adapter.urbridge.URBridge getSecNameFromUniqueID
    com.ibm.websphere.wim.exception.EntityNotFoundException: CWWIM4001E The '3958cdfe-fcb4-4b77-86cb-8dd9acfcb9f5' entity was not found.
    at com.ibm.ws.wim.adapter.urbridge.URBridge.getSecNameFromUniqueID(URBridge.java:993)
    at com.ibm.ws.wim.adapter.urbridge.URBridge.validateEntity(URBridge.java:921)
    at com.ibm.ws.wim.adapter.urbridge.URBridge.get(URBridge.java:428)
    at com.ibm.ws.wim.ProfileManager.retrieveEntityFromRepository(ProfileManager.java:2663)
    at com.ibm.ws.wim.ProfileManager.retrieveEntity(ProfileManager.java:2809)
    at com.ibm.ws.wim.ProfileManager.getImpl(ProfileManager.java:1541)
    at com.ibm.ws.wim.ProfileManager.genericProfileManagerMethod(ProfileManager.java:319)
    at com.ibm.ws.wim.ProfileManager.get(ProfileManager.java:372)
    at com.ibm.websphere.wim.ServiceProvider.get(ServiceProvider.java:348)
    at com.ibm.websphere.wim.client.LocalServiceProvider.get(LocalServiceProvider.java:364)
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler$2.run(StandardSecureWIMHandler.java:187)
    at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5306)
    at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5394)


    Solution: Follow the steps mentioned for Business Space Configuration and user access configuration for Business Space in the developer’s guide.

  • Problem: For Business Process Manager Banking Pack V7.5 on IBM Business Process Manager V7.5.1, the execution of the New Account Opening Solution Scenario through iLog Rules throws exceptions.


    Solution: To resolve this issue, comment or delete calls to the copyNamespaceDeclarations template by completing the following steps:
    1. Go to the DocumentCheckListILOGRule-MM module.

    2. Open the Response Mediation flow .xsl file.

    3. Comment calls made to the copyNamespaceDeclarations template.

    4. Save, build, and redeploy DocumentCheckListILOGRule-MMApp.

  • Problem: For Business Process Manager Telecom Pack V7.5 on IBM Business Process Manager V7.5.1, executing the OOSJSIDTransformationTest project Test Suites throws an exception.


    Symptom: The following exception is thrown:
    com.ibm.wbit.comptest.ctnative.service.CTRuntimeException: java.lang.NullPointerException
    at com.ibm.wbit.comptest.ctnative.runtime.service.CTServiceProxy.doInvoke(CTServiceProxy.java:204)
    at com.ibm.wbit.comptest.ctnative.runtime.service.CTServiceProxy$1.run(CTServiceProxy.java:126)
    at java.security.AccessController.doPrivileged(AccessController.java:224)
    at javax.security.auth.Subject.doAs(Subject.java:495)
    at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:131)
    at com.ibm.wbit.comptest.ctnative.runtime.service.CTServiceProxy.invoke(CTServiceProxy.java:120)
    at $Proxy171.invoke(Unknown Source)
    at test.OSSJSIDTransformationTestSuite.test_transformSidToOssj(OSSJSIDTransformationTestSuite.java:61)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


    Solution: Creating a new test component request should solve the issue. Complete the following steps:
    1. Import the OSSJToSIDModule PI project into IBM Integration Designer V7.5.1.

    2. Build the workspace and ensure that errors are not displayed.

    3. Expand OSSJToSIDModule.

    4. Double-click and open the Assembly Diagram.


      Right-click OssjSidTransformationTransformOssjToSidExport and select Test Component.

    5. Create a new Test Case. For the inputs required within the test case, refer to existing test case present within the project.( OSSJSIDTransformationTest).

    6. Save and Run the request to execute.


    Note
    : Ensure this Common Service is successfully deployed to the process server with required configuration settings.

  • Problem: Changing the user displayname mapping in the WIMCONFIG.xml file does not work.


    Symptom: Setting the propertyForInput and propertyForOutput to displayName in the userDisplayNameMapping element should return display name. However, changing the value results in the following exception:
    wle_security E CWLLG2015E: An unexpected runtime exception occurred. See exception for more details. Error: null.
    com.ibm.ws.wim.security.authz.AuthPrivilegedException: An error occured while performing a task as the super user
    at com.ibm.ws.wim.security.authz.ProfileSecurityManager.runAsSuperUser(ProfileSecurityManager.java:970)
    at com.ibm.ws.wim.registry.WIMUserRegistry.getUserDisplayName(WIMUserRegistry.java:481)
    at com.ibm.ws.security.registry.UserRegistryImpl.getUserDisplayName(UserRegistryImpl.java:445)
    at com.ibm.websphere.security._UserRegistry_Stub.getUserDisplayName(_UserRegistry_Stub.java:327)
    at com.lombardisoftware.userorg.WSAbstractUserRegistryModule.getPrincipalDescription(WSAbstractUserRegistryModule.java:237)
    at com.lombardisoftware.userorg.AbstractAccessControllerManager.getPrincipalDescription(AbstractAccessControllerManager.java:130)
    at com.lombardisoftware.userorg.UserOrgModule.getPrincipalDescription(UserOrgModule.java:197)
    at com.lombardisoftware.server.core.UserCore.getOrCreateUserInfoObject(UserCore.java:115)
    at com.lombardisoftware.server.core.UserCore.getOrCreateUserInfoObject(UserCore.java:96)
    at com.lombardisoftware.server.core.UserCore.getOrCreateUserId(UserCore.java:91)


    Solution: Applying the following listed WebSphere Application Server interim fixes should resolve this issue:
  • Problem: For Business Process Manager Industry Packs V7.5 on Business Process Manager V7.5.1, the execution of BPDs through Microsoft Internet Explorer 8 browser is not successful.


    Symptom: Some validations are not executed for Date of birth. Options displayed might be incorrect and gives a validation error at some place even after entering right values.


    Solution: Fix the wicpCommScript.js file, which is in located in the “WICP Common Data” toolkit, or run in the Mozilla Firefox browser.


    Current wicpCommScript.js file:
    var oldVldForm;
    dojo.addOnLoad(function(){
    searchSetVld();
    oldVldForm = vldForm;
    vldForm = function(theForm){ return wicpVldForm(theForm); }
    });


    Functioning patched wicpCommScript.js file:
    var oldVldForm;
    dojo.addOnLoad(function(){
    searchSetVld();
    oldVldForm = vldForm;
    vldForm = function(theForm){ return wicpVldForm(theForm); };
    });


    The fix needs to be done in the toolkit source by adding the semi-colon to the second last line in the previous code block.

  • Problem: For Business Process Manager Telecom Pack V7.5 on IBM Business Process Manager V7.5.1, after importing the Assurance toolkit file in Process Designer, the validation errors are displayed.


    Symptom: After importing Telecom specific Assurance toolkit file in Process Designer and opening it in Process Designer the following validation error displays:
    Managed file is unreachable: [61.c09141cf-bf7e-45bd-a72e-f2b90090df05:null]


    Solution: To resolve this issue, complete the following steps:
    1. Import the Assurance toolkit into Process Designer.

    2. Click Assurance toolkit > Manage, and check the box for Allow user to update toolkit.

    3. Click Snapshots > Open in Designer.

    4. Click the validations errors and double-click Enrich Customer Problem to open.

    5. Click Coaches tab and click <#= tw.resource.TelecomCommonResource.coachAdditionalInformationTroubleTicket #> from the coach.

    6. In properties, select the button besides CSS Override.

    7. Select TelecomLombardi.css and click Save.

    8. Similarly repeat steps 4 to 7 for the other listed validation errors.

  • Problem: Displays validation errors, when you install a Process application through scripts.


    Symptom: When you try to install a process application through scripts and upgrade the system data toolkit to 7.5.1, you might see the following validation error:
    The contract of ''BenefitsEligibilityInquiryAIS_invoke'' has changed and may no longer match the implementation provided by Integration Designer. Update the implementation in Integration Designer and republish it to synchronize.


    Solution: To overcome this validation error, you must replicate the process application project into IBM Integration Designer and republish the process application. After installing the Industry Packs Process applications through install scripts and upgrading the System Data toolkit to 7.5.1, complete the following steps:
    1. Launch IBM Integration Designer and switch to the Process Center perspective.

    2. Provide the URL (http://<hostname>:<port>/Process Center) and user credentials to replicate into IBM Integration Designer.

    3. Open the replicated process application project in the workspace and wait until it builds the project in the workspace.

    4. Right-click the process application project and select Refresh and Publish. It will start updating Process Center server.

    Note: You will also see the name of the Process application prefixed with [changed] as shown below:

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Business Process Manager Industry Packs
General

Software version:

7.5

Operating system(s):

Windows

Software edition:

All Editions

Reference #:

7024319

Modified date:

2012-03-09

Translate my page

Machine Translation

Content navigation