As your business environment evolves, it may be necessary to change
which WebSphere® MQ
destinations a Service Component Architecture (SCA) module communicates with.
Use this task to effect those changes.
Before you begin
You must know which Service Component Architecture (SCA) modules use
the WebSphere MQ
destinations you are changing. By default, these destinations are created
when you install an SCA module into a server or cluster. The destinations
are of the form:
- For a one-way export:
- modulename.exportname_MQEXPORT_CF
- modulename.exportname_MQ_RECEIVE_D
- In addition, for a two-way export:
- modulename.exportname_MQ_SEND_D
- For a one-way import:
- modulename.importname_MQIMPORT_CF
- modulename.importname_MQ_SEND_D
- In addition, for a two-way import:
- modulename.importname_MQ_RECEIVE_D
This task assumes that you are using the administrative console to change
the configuration.
Restrictions: When changing
the destinations keep the following in mind:
- You must configure queue destinations with the target client set to MQ.
- You must use a TCP/IP client connection to connect to WebSphere MQ. See WebSphere MQ Intercommunication for details.
- You cannot use channel compression.
- You must set any necessary channel exits for correct data handling by
setting them in the Custom Properties of the WebSphere
MQ messaging provider > WebSphere MQ connection factory objects :
- You must set the custom property SENDEXIT to have
the value com.ibm.ws.sca.internal.mq.exit.MQInternalSendExitImpl.
- You must set the custom property RECEXIT to have
the value com.ibm.ws.sca.internal.mq.exit.MQInternalReceiveExitImpl.
- You must set the optional custom property SENDEXITINIT to
a text string of your choice. Setting this property helps you identify the
exit in a trace.
- You must set the optional custom property RECEXITINIT to
a text string of your choice. Setting this property helps you identify the
exit in a trace.
- You cannot use the same connection factories for WebSphere MQ and Java
Message Service (JMS) MQ bindings as the exits will inhibit the JMS MQ bindings.
Why and when to perform this task
After deploying SCA modules, you may need to change the WebSphere MQ
destinations to meet new business requirements.
Steps for this task
- Stop all applications that use the destinations you
are changing. Use the steps described in "Administering enterprise
applications."
- Allow the destination to complete processing the messages in progress.
- Display the WebSphere MQ destinations. Navigate
to this page in the administration console using Resources > JMS
Providers > WebSphere MQ > WebSphere MQ queue destinations
- Select the scope of the destinations you are changing.
If
the SCA modules containing the destinations are installed on single servers,
select Server scope.
If the SCA modules containing
the destinations are installed on clusters, select Cluster scope.
- Select the destination to change from the list.
- Change the fields on the next page to the new values.
- Repeat steps 5 and 6 for each destination you are
changing.
- Save the configuration changes.
What to do next
Restart the applications you stopped in step
1.
Last updated: Wed 06 Dec 2006 07:08:08
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)