Publishing a new unit test server configuration

Before you start:

Before you can publish (deploy) a configuration using rapid application development (RAD), you need to create a Configuration Manager and a WebSphere MQ listener must be running. You must also create a domain, add a broker to that domain and create an execution group within the broker.

  1. From the Broker Application Development perspective, click Run On Server in the toolbar, or right-click the file that you want to publish, and click Run On Server. The Server Selection window appears.
  2. Click Create a new server.
  3. Select the file that you want to use and select the Server Type.
  4. Click Set server as project default.
  5. Click Next.
  6. Either use an existing Configuration Manager connection file or specify the connection parameters. Default values are shown if you do not have any connection files in the workbench.
    1. Enter the name of the WebSphere MQ queue manager that the Configuration Manager is using. This property is mandatory.
    2. Enter the host name or IP address of the machine on which the Configuration Manager is running (the default is localhost). This property is mandatory.
    3. Enter the TCP port on which the WebSphere MQ queue manager is listening (the default is 1414). This property must be valid positive number.
    4. Optional: Enter the name of the Security Exit required to connect to the WebSphere MQ queue manager. This property must be a valid Java classname, but you can leave this box blank if it is not applicable to your domain connection.
    5. Optional: Enter the location of the JAR file for the Security Exit required to connect to the WebSphere MQ queue manager. Use the Browse button to find the file location. You can leave this box blank if it is not applicable to your domain connection.
  7. Click Next.
  8. Specify the broker that you want to use and the name of the execution group you are creating. The execution group name must be unique. The name defaults to your user ID.
  9. Click Next. (Do not click Finish at this point.)
  10. The available projects are listed. Select the message flows and message sets that you want to assign to the execution group.
  11. Click Finish.

The workbench publishes (deploys) the message flows and message sets to the broker on the test server. You should get a message saying Publishing successful. This means that the deployment has been successfully initiated; look in the Event Log to check for any possible error messages and check the contents of your execution group to confirm that deployment was successful.

Note: You can also use the Debug on Server action to publish your new unit test server configuration. The difference is that, after the configuration has been published, the flow debugger is attached to the runtime environment, and the Flow Debug perspective opens so that you can debug your message flows or message sets.
Related concepts
Rapid application development (RAD)
Related tasks
Creating a Configuration Manager on Windows
Creating a domain connection
Adding a broker to a broker domain
Using rapid application development (RAD)
Starting the WebSphere MQ channels and listeners
Adding an execution group to a broker
Related reference
Broker Administration perspective