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.
The following topics explain how to deploy modules to the test environment
and work with the server tools:
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.
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 configuration editor and then edit some basic settings, such as modifying a port number or enabling basic security. Or you may want to open the administrative console and then edit some advanced settings, such as configuring the behavior of human tasks at runtime or enabling advanced security.
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.
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.
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.
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.
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.