WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
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, WebSphere Message Broker 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
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
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 Tivoli License Manager 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
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 Other folder, and click Project Interchange. For more information, see , expand the Importing resources from previous versions.
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, WebSphere Message Broker does not connect to the SAP gateway
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
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.