Configure the integrated test environment

Application Testing and Debugging
Websphere Integration Developer v612
Contact us...

1. Configure the integrated test environment
   1. Deploying modules to the test environment

 

Configure the integrated test environment

 

In WebSphere® Integration Developer, the integrated test environment features runtime support for WebSphere Process Server, or WebSphere Enterprise Service Bus, or both, depending on the test environment profiles that you chose to install when you installed WebSphere Integration Developer.

WebSphere Process Server enables you to run business integration components that cannot be run on any other type of server, such as BPEL business processes, human tasks, business state machines, business rules, and other components. You can also run mediation flows that are contained in mediation modules. By comparison, mediation flows are the only business integration component that you can run on WebSphere Enterprise Service Bus. The deployment documentation provides sufficient information about the integrated test environment to enable you to deploy your modules. However, if you want to learn more about WebSphere Process Server or WebSphere Enterprise Service Bus, see the documentation at the IBM WebSphere Business Process Management Version 6.1 information center.

WebSphere Integration Developer extends the deployment capabilities of the Rational® Application Developer base on which it is built. Similarly, the WebSphere Integration Developer deployment documentation extends and supplements the deployment documentation of Rational Application Developer.

Deploying modules to the test environment

In WebSphere® Integration Developer, you can deploy modules to the test environment and work with server tools that enable you to perform such tasks as creating test servers, editing server configurations, and starting and stopping servers.

  

1. Creating servers in the test environment
   If you chose to install the WebSphere Process Server and WebSphere Enterprise Service Bus test environment profiles when you installed WebSphere Integration Developer, then you will already have default test environment servers. However, if you deleted one or both of these default servers or if you are working with a standalone installation of WebSphere Process Server or WebSphere Enterprise Service Bus, you will need to create one or more test environment servers for testing your modules.
2. Editing server configurations in the test environment
   There may be occasions when you want to edit a server configuration. For example, you may want to open the server administrative console and then edit some properties, such as configuring the behavior of human tasks at run time. Or you may want to open the WebSphere Integration Developer server configuration editor and then edit some basic settings, such as modifying a port number.
3. Starting servers in the test environment
   Before you can create a running instance of a component in WebSphere Integration Developer, you need to start the server.
4. Adding modules to test environment servers
   Before you can test your modules on a test environment server, you need to add the modules to the server.
5. Publishing modules to test environment servers
   In WebSphere Integration Developer, you will occasionally need to publish modules to a running test environment server. This effectively redeploys the modules and allows the running server to pick up changes that you have made to the components of your modules.
6. Publishing changed resources to a server
   If new or changed resources exist in your workspace that have not yet been published to the server, the state of the server in the Servers view will be Republish. If you want to see the specific resources that are new, changed, or deleted and then decide whether to publish the updates to the server, you can open the View and Publish Changes to Server dialog box.
7. Removing modules from servers
   From time to time, you will want to remove modules from your servers. For example, if you have modules that you no longer need to test, you should consider removing them from the server so that they do not needlessly impact the performance of the server.
8. Restarting servers in the test environment
   In WebSphere Integration Developer, you may encounter situations where you need to restart a running test environment server. For example, you will probably need to restart a server if you make changes to the server configuration while the server is running.
9. Stopping servers in the test environment
   Whenever you finish using a test environment server in WebSphere Integration Developer, you should stop it. This ensures that the server will not unnecessarily impact the performance of other tools in the workbench or the computer that it is running on.
10. Creating or resetting default server profiles
    A default server profile is a test environment server profile that is created when the WebSphere test environment is installed with WebSphere Integration Developer. In the Servers view, you can choose to create or reset a default server profile for either WebSphere Process Server or WebSphere Enterprise Service Bus. For example, you may now want to create a default server profile that you earlier chose not to have created when you installed the WebSphere test environment. Or you may need to reset an existing default server profile that is no longer functioning correctly.