Tasks to complete after generating the Service Proxy: static endpoint
pattern
Tasks that you must complete after you have generated the pattern.
If you are using the Web Based Service Proxy
pattern these steps will be performed for you.
Create the broker archive (BAR) file. The message flow must be added to a broker archive file.
Configure the broker archive file. Further configuration of the message flow in the broker archive file
is not required
before you deploy the message flows for your Service Proxy: static endpoint pattern instance,
but you might want to review some of the default options and configure changes for your environment.
In the Manage page of the Broker Archive
editor:
Optional: Use the
RequestLoggingOn user-defined property to
select whether logging requests are on or off for the message flow.
Optional: Use the
ResponseLoggingOn user-defined property to
select whether logging replies are on or off for the message flow.
Optional: Use the ErrorLoggingOn
user-defined property to select whether
error messages are generated.
Optional: You can also change any of the configurable properties
in the broker archive, for example, properties for security or creating
additional instances. You must ensure that any values that you
change do not impact the behavior of the pattern instance.
If the transport defined in the WSDL file is HTTPS,
additional SSL configuration is required,
see "Implementing SSL Authentication" in the WebSphere Message Broker documentation.
Create queues. When you apply the pattern, a list of WebSphere MQ queues is generated with
queue names and queue manager names, these WebSphere MQ queues must be created if they do
not already exist. All the message settings that are required by the pattern are
set explicitly on the messages and are not dependent on queue settings.
In the summary file, view the list of queues that you must create. The summary file
is located in the Pattern Configuration folder of the
InstanceName pattern instance project.
Create WebSphere MQ resources. You can create WebSphere MQ resources
either on the command line, by using programs and utilities such as runmqsc,
or by using the WebSphere MQ Explorer graphical interface.
For more information about creating
WebSphere MQ resources, see WebSphere MQ Intercommunication,
available on the
WebSphere MQ
library web page.
Deploy the BAR file. The message set containing the deployable WSDL must be deployed
by using the same, or another, BAR file.
The address of the proxy service is determined after deployment and is published to requesters.
This information can be obtained by using the mqsireportproperties
command to determine the HTTPConnector
properties for the execution group.