IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Resolving problems when developing message flows with WebSphere Adapters nodes

Advice for dealing with common problems that can arise when you develop message flows that contain WebSphere® Adapters nodes.

WebSphere Adapters nodes

Error messages BIP3414 and BIP3450 are issued when you deploy a WebSphere Adapters input node
Error messages are issued when classes cannot be found, or when problems occur with Java initialization
The WebSphere Adapters are not visible when you run ITLM
A message flow with an SAPRequest, SiebelRequest, or PeopleSoftRequest node has deployed successfully, but message BIP3540 is issued indicating that connection failed

SAP nodes

You have deployed an SAP inbound adapter but do not receive expected messages
You have imported an existing project into your workspace, but messages are issued when you try to build SAP message sets
An error is issued when you use the message set that is generated by the Adapter Connection wizard
When you run the SAP samples on Linux or UNIX, IBM Integration Bus does not connect to the SAP gateway
SAP inbound messages (ALE and BAPI) appear to be missing
When two ALE inbound modules use the same RFC program ID with SAP JCo version 3.0.2, NullPointer exceptions are logged in the JCo trace and the Adapter does not receive IDocs

Siebel nodes

You are using a SiebelInput node with the delivery type set to unordered, and error message BIP3450 is issued with a NullPointer exception

JD Edwards nodes

Error message BIP3450 is issued when you include a JDEdwardsRequest node in a message flow and try to connect to a JD Edwards EnterpriseOne server

Error messages BIP3414 and BIP3450 are issued when you deploy a WebSphere Adapters input node

Scenario: When you deploy a message flow that contains a SiebelInput node, error message BIP3414 is issued.
Explanation: The error messages explain that the SiebelInput node could not register with the adapter component to receive events. This problem can be caused when the broker does not know where to find the client libraries for the Siebel Enterprise Information Service (EIS). You might also encounter this problem if you are using the WebSphere Adapter for Siebel on an unsupported operating system.
Solution: Use the mqsireportproperties and mqsichangeproperties commands to configure the broker with the location of the Siebel client libraries, as described in Preparing the environment for WebSphere Adapters nodes.

Error messages are issued when classes cannot be found, or when problems occur with Java initialization

Scenario: You are deploying WebSphere Adapters, and error messages are issued that indicate that classes cannot be found, or problems are occurring with Java™ initialization. BIP3521 and BIP3522 error messages might also be issued.
Explanation: The SAP, Siebel, and PeopleSoft adapters need client libraries from the manufacturer of the Enterprise Information System (EIS). If these libraries are missing, not installed correctly, or at an incorrect level, errors are issued.
Solution: To solve this problem, complete the following steps.
1. On the broker that you are using to change the configurable service of the adapter, run the mqsichangeproperties command to identify the location of the Java and native libraries.
2. Ensure that the libraries are installed correctly, are valid for your operating system, and have the correct permission so that the broker can access them.
3. Ensure that your operating system is supported by IBM® Integration Bus and the EIS provider. For details about supported operating systems, visit the IBM Integration Bus Requirements Web site.

The WebSphere Adapters are not visible when you run ITLM

Scenario: The adapter is not visible when you run the IBM Tivoli® License Manager (ITLM).
Explanation: If you want to use ITLM with the WebSphere Adapters, you must activate the ITLM file for each adapter.
Solution: Follow the instructions in Activating IBM License Metric Tool for WebSphere Adapters.

A message flow with an SAPRequest, SiebelRequest, or PeopleSoftRequest node has deployed successfully, but message BIP3540 is issued indicating that connection failed

Scenario: From an SAPRequest, SiebelRequest, or PeopleSoftRequest node, an exception is thrown to indicate that the node is unable to make a connection even though the message flow has deployed successfully. The exception contains message BIP3540 with inserted text that indicates that connection failed. For example, for SAP, the inserted text is:

Exception in connecting to SAP:Connect to SAP gateway failed 
Connect_PM GWHOST= invalidhost.test.co, GWSERV=sapgw00, ASHOST= invalidhost.test.co, 
  SYSNR=00
LOCATION CPIC (TCP/IP) on local host ERROR partner not reached (host
  invalidhost.test.co, service 3300) TIME Mon Dec 01 16:43:52 2008 RELEASE 640 
COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8719 
DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10061 ERRNO TE

For PeopleSoft, the inserted text is:

001DOWNbea.jolt.ServiceException: Invalid Session

Explanation: The connection details are not verified when the message flow is deployed. For request nodes, the connection is made at first use.
Solution: If you have configured a configurable service for this adapter, review the connection properties on that configurable service and review the text in the BIP3540 message to determine if the connection properties are incorrect. If the properties are incorrect, use the mqsichangeproperties command to correct them or use the mqsideleteconfigurableservice command to revert to the properties that are set on the adapter. Reload the integration server or stop and restart the broker.
If no configurable service exists for this adapter, review the connection properties on the adapter. If the properties are incorrect, correct them and redeploy the adapter. Alternatively, use the mqsicreateconfigurableservice command to create a new configurable service with the correct properties to override the properties that are set on the adapter.

You have deployed an SAP inbound adapter but do not receive expected messages

Scenario: You have deployed an SAP inbound adapter but do not receive the IDoc messages that you expected to receive.
Explanation: If you have not received IDoc messages from SAP, it is possible that deployment was unsuccessful or the SAP server has not started.
Solution: Check user trace for message BIP3484 occurring at the time of deployment. The adapter component writes diagnostic information to this message, in an insert that begins "CWYAP...". If this message is issued, it explains the cause of the problem.

You have imported an existing project into your workspace, but messages are issued when you try to build SAP message sets

Scenario: You have imported an existing project into your workspace, but when you try to build an SAP message set, you see the message set compile error message BIP0182.
Explanation: This error occurs when you choose the option to "Import existing projects into your workspace" from the Import dialog box. By choosing this option when you import, a link is created from the workspace to the existing projects in an external location and a required file is not available to the workspace. To copy the entire project into your workspace, use the option to import the Project Interchange (PI) file.
Solution: When you import an exiting SAP project into your workspace, click File > Import, expand the Other folder, and click Project Interchange. For more information, see Importing resources from previous versions.

An error is issued when you use the message set that is generated by the Adapter Connection wizard

Scenario: You run the Adapter Connection wizard and select an inbound SAP IDoc. You run the wizard again, but this time you select an outbound SAP IDoc. When you use the message set that is generated, the following error is issued:

'Selector exception caught from generateEISFunctionname', 'commonj.connector.runtime.SelectorException: 
commonj.connector.runtime.SelectorException: For the IDoc type SapYwmspgi01, operation key=YWMSPGIWMS not 
found using the application-specific information {Create={MsgType=, MsgCode=, MsgFunction=}} verify appropriate 
combination of MsgType, MsgCode, MsgFunction is set in SapYwmspgi01, application-specific information.

Explanation: If you run the Adapter Connection wizard for an inbound SAP IDoc, then you run the wizard again for an outbound SAP IDoc, the outbound IDoc definition replaces the inbound IDoc definition. Information that is stored in the inbound definition is used to map MsgType, MsgCode, and MsgFunction to a method binding. The outbound definition does not contain these mappings, so processing of the inbound IDoc fails.
Solution: To avoid this error, ensure that inbound and outbound SAP IDocs have different names if they are stored in the same message set.

When you run the SAP samples on Linux or UNIX, IBM Integration Bus does not connect to the SAP gateway

Scenario: When you run the SAP samples on Linux or UNIX, the message flow deploys successfully, but a connection is not established between IBM Integration Bus and the SAP system. You might see the following error message:
```
message: Connect to SAP gateway failed
Connect parameters: TPNAME=SAMPRFC GWHOST=sapdev10 GWSERV=sapgw00
ERROR service 'sapgw00' unknown
```
Explanation: For the SAP Java Connector (SAP JCo) to communicate across the network, you need to configure the TCP/IP service. If you have installed a working SAP GUI on your workstation, the TCP/IP service is configured as part of the installation. If you have not installed an SAP GUI, you must configure the TCP/IP service manually so that the SAP samples run successfully.
Solution: Locate the services file in /etc/services and edit it so that it includes the appropriate gateway service IDs and the port numbers for the TCP/IP service in the format sapgwSID portnumber/tcp, where SID is the SAP system ID. For example:
```
sapgw00		3300/tcp
sapgw01		3301/tcp
sapgw02		3302/tcp
```
and so on.
For more information about TCP/IP configuration, see the Network Integration section of the SAP Service Marketplace.

SAP inbound messages (ALE and BAPI) appear to be missing

Scenario: SAP inbound messages (ALE and BAPI) appear to be missing. You might find that every other message does not reach the broker but no errors are issued.
Explanation: This problem is typically caused when two brokers share the same program ID (SAP RFC Destination). For example, a developer has deployed a message flow, but someone else has used the same broker archive (BAR) file without having changed the program ID.
Solution: Ensure that no other brokers are running with the same program ID. Use SAP transaction SMGW to determine whether other brokers are connected to the SAP system.

When two ALE inbound modules use the same RFC program ID with SAP JCo version 3.0.2, NullPointer exceptions are logged in the JCo trace and the Adapter does not receive IDocs

Scenario: When two ALE inbound modules use the same RFC program ID with SAP JCo version 3.0.2, NullPointer exceptions are logged in the JCo trace and the Adapter does not receive IDocs.

The following example shows a typical exception in the JCo trace.

JCoDispatcherWorkerThread [16:44:42:140]: [JCoApi] Dispatcher.getNextListener() returns dispatch next call rfc handle(1) for null
JCoDispatcherWorkerThread [16:44:42:140]: [JCoApi] caught Throwable in DispatcherWorker.run() while trying to dispatch a request java.lang.NullPointerException
	at java.util.Hashtable.get(Hashtable.java:518)
	at com.sap.conn.jco.rt.DefaultServerManager$DispatcherWorker.run(DefaultServerManager.java:268)
	at java.lang.Thread.run(Thread.java:735)

JCoDispatcherWorkerThread [16:44:42:140]: [JCoApi] Dispatcher.getNextListener() returns no calls

Explanation: SAP JCo version 3.0.2 does not support the use of two ALE inbound modules with the same RFC program ID.
Solution: To solve this problem, download a hotfix from SAP; the SAP ticket reference number is 584247/2009.

You are using a SiebelInput node with the delivery type set to unordered, and error message BIP3450 is issued with a NullPointer exception

Scenario: You are using a SiebelInput node, you have set the delivery type to unordered in the Adapter Connection wizard, and the minimum number of connections is 1 or less. The following exception is shown in user trace: RecoverableException BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is java.lang.NullPointerException.
Explanation: When using unordered events, the minimum connections (MinimumConnections) and maximum connections (MaximumConnections) properties must be greater than 1 for event delivery to be successful.
Solution: Set the MinimumConnections and MaximumConnections properties on the Adapter Connection wizard to values greater than 1. For example, set the minimum number of connections to 2 and the maximum number of connections to 4.

Error message BIP3450 is issued when you include a JDEdwardsRequest node in a message flow and try to connect to a JD Edwards EnterpriseOne server

Scenario: You have created a message flow that contains a JDEdwardsRequest node, but error message BIP3450 is issued, indicating that the node is unable to connect to the JD Edwards EnterpriseOne server.

Explanation: This error message indicates that the JDEdwardsRequest node is trying to connect to the JD Edwards EnterpriseOne server but is unable to do so. This error can be caused by the following situations.

The JD Edwards EnterpriseOne server is not running.
The JD Edwards adapter has been configured with incorrect connection details; for example, the name of the JD Edwards EnterpriseOne Environment to which to connect.
The JDBC drivers that are required to connect to the JD Edwards EnterpriseOne server are missing from the class path. The following table lists the required JDBC driver files for each database.

Database	JDBC driver files	Implementation class
Oracle	tsnames.ora classes12.zip	oracle.jdbc.driver.OracleDriver
SQLServer	sqljdbc.jar	com.ibm.microsoft.sqlserver.jdbc.SQLServerDriver
AS/400	jt400.jar	com.ibm.as400.access.AS400JDBCDriver
DB2® Type-2 (JDK 1.4/1.5)	db2java.zip	com.ibm.db2.jdbc.app.DB2Driver
DB2 Type-4 (JDK 1.4/1.5)	db2jcc.jar db2jcc_license_cu.jar	com.ibm.db2.jcc.DB2Driver
DB2 Type-4 (JDK 1.6)	db2jcc4.jar	com.ibm.db2.jcc.DB2Driver

Solution: Ensure that the following conditions have been met.
- The JD Edwards EnterpriseOne server is running.
- The JD Edwards adapter has been configured with the correct connection details.
- The drivers that are required to connect to the JD Edwards EnterpriseOne server are in the class path.

au16538_.htm |

Last updated Friday, 21 July 2017