|
Oracle® Application Server Integration InterConnect Adapter for WebSphere MQ Installation and User's Guide
10g Release 2 (10.1.2) B14072-02 |
|
 Previous |
 Next |
|
Oracle® Application Server Integration InterConnect Adapter for WebSphere MQ Installation and User's Guide
10g Release 2 (10.1.2) B14072-02 |
|
|
Previous |
Next |
This appendix provides answers to following frequently asked questions about the WebSphere MQ adapter.
How do I know the WebSphere MQ adapter has started properly?
The WebSphere MQ adapter did not start properly. What went wrong?
My WebSphere MQ adapter is not starting. What could be the reason?
Is it possible to edit the WebSphere MQ adapter configuration settings created during installation?
I am getting a JMS-nnnn error when the WebSphere MQ adapter is starting up. What is wrong?
View the log.xml file located in the time-stamped subdirectory of the WebSphere MQ adapter log directory:
| Platform | Directory |
|---|---|
| UNIX | ORACLE_HOME/integration/interconnect/adapters/Application/log/timestamp_in_milliseconds
|
| Windows | ORACLE_HOME\integration\interconnect\adapters\Application\log\timestamp_in_milliseconds
|
If there are no exceptions, then the WebSphere MQ adapter has started properly.
View the exceptions in the WebSphere MQ adapter log file (log.xml). The exceptions should provide information about what went wrong. It is possible that the WebSphere MQ adapter is unable to connect to the repository. Ensure the repository is started properly. The WebSphere MQ adapter will connect to the repository once it is started properly. You do not need to restart the Adapter.
|
See Also: Oracle Application Server Integration InterConnect User's Guide for instructions on starting the repository on UNIX and Windows |
One reason can be that Oracle Wallet does not contain the password information corresponding to your application name. For example, during installation you defined the application name as myMQApp. Later, you changed the application name in iStudio to MQApp. In such case, you need to specify the password corresponding to the new application name MQApp in the Oracle Wallet. You can create password by using the oraclewallet command.
Yes, edit the parameters in the adapter.ini file in the following directory:
| Platform | Directory |
|---|---|
| UNIX | ORACLE_HOME/integration/interconnect/adapters/Application/
|
| Windows | ORACLE_HOME\integration\interconnect\adapters\Application\
|
The WebSphere MQ adapter caches information from iStudio. The information is stored in the repository locally. If you change something in iStudio and want to view the change in the run time, then you need to stop the WebSphere MQ adapter, delete the WebSphere MQ adapter cache files, and restart the WebSphere MQ adapter.
The WebSphere MQ adapter has a persistence directory which is located in the WebSphere MQ adapter directory. Deleting this directory when the WebSphere MQ adapter has been stopped should make it obtain the new metadata from the repository when started.
OracleAS Integration InterConnect uses Oracle Wallet Manager to maintain system passwords. When you install OracleAS Integration InterConnect, Oracle Wallet Manager is also installed and a password store is created. All passwords used by OracleAS Integration InterConnect components are stored in the password store. The password is stored in the Oracle Wallet in the following format:
ApplicationName/password
The ApplicationName is the name of the application, which is extracted from the adapter.ini file of the corresponding adapter. In the adapter.ini file, the application parameter specifies the ApplicationName to which this adapter connects. The password for the application is also retrieved from the adapter.ini file.
The number of entries is dependent on the type of adapter. For example, DB Adapter needs two entries whereas AQ Adapter needs only one entry. The following table lists the entries that will be created for each adapter:
| Adapter | Entry In Oracle Wallet |
|---|---|
| AQ | ApplicationName/aq_bridge_password
|
| HTTP | ApplicationName/http.sender.password
|
| HTTP | ApplicationName/sender.wallet_password
|
| SMTP | ApplicationName/smtp.receiver.password
|
| MQ | ApplicationName/mq.default.password
|
| FTP | ApplicationName/file.sender.password
|
| FTP | ApplicationName/file.receiver.password
|
| DB | ApplicationName/db_bridge_schema1_password
|
| DB | ApplicationName/db_bridge_schema1_writer_password
|
You can create, update, and delete passwords using the oraclewallet command. When you run the command, it prompts you for the admin password.
You can use the following commands to manage your passwords:
List all passwords in the store
oraclewallet -listsecrets
Create a password
oraclewallet -createsecret passwordname
For example, to create a password for the hub schema:
oraclewallet -createsecret hub_password
View a password
oraclewallet -viewsecret passwordname
For example, to view the password for the hub schema:
oraclewallet -viewsecret hub_password
Update a password
oraclewallet -updatesecret passwordname
For example, to update the password for the hub schema:
oraclewallet -updatesecret hub_password
Delete a password
oraclewallet -deletesecret passwordname
For example, to delete the password for the hub schema:
oraclewallet -deletesecret hub_password
Look up the error code in the IBM WebSphere MQ for Java guide Messages Appendix and correct any mistakes for the WebSphere MQ connection information in adapter.ini. The following lists some common error codes:
2009 MQRC_CONNECTION_BROKEN: The connection to the queue manager has been lost. This can occur because the queue manager has ended. All previous handles are now invalid. As a result, the WebSphere MQ adapter should be restarted.
2030 MQRC_MSG_TOO_BIG_FOR_Q: The message length is greater than the maximum for the queue. Increase MaxMsgLength for the queue (WebSphere MQ Administrator).
2031 MQRC_MSG_TOO_BIG_FOR_Q_MGR: The message length is greater than the maximum allowed by the remote queue manager. This error also occurs if the message size is larger than the maximum message size allowed by a channel through which the message is to pass.
2035 MQRC_NOT_AUTHORIZED: The user is not authorized to perform the operation attempted. Make sure the mq.default.user and mq.default.password parameters in adapter.ini are correct.
More error codes can be found at the following url: http://www-4.ibm.com/software/ts/mqseries/library/manuals/csqfao/CSQFAO1P.HTM.
The means that some outbound messages received from WebSphere MQ did not parse successfully with any of the registered D3L files. Either one or more D3L files should be corrected or the WebSphere MQ sending agent, which enqueued the message on the outbound queue, should correct the messages so they conform to one of the D3L files. If you configure the mq.default.receiver.exception.uri parameter in the adapter.ini file, then the 'failed' messages will be enqueued on the configured exception queue.
The complete text of the error message is "MQMessageSender_run: The following exception occurred while invoking oracle.oai.agent.adapter.sdk.Agent.createMessageObject(xml). If the Published Message Type in iStudio was XML, then try instead to use the Message Type Generic, setting the Object name to be the root element of the XML document."
The error message essentially also provides the solution to this problem.
This is a benign warning message from the WebSphere MQ Java layer which can be avoided by adding the /opt/mqm/java/lib directory to the Java CLASSPATH before starting the WebSphere MQ adapter (modifying the start script).
