When you invoke an operation, the integration test client detects
whether your module needs to be deployed to the server. If the module is not
deployed, the integration test client automatically opens the Deployment Location
wizard to enable you to easily deploy the module and start the server (if
it is not already started).
For the integration test client to detect the deployment state of
your module, you need to have invoked an operation by clicking the Continue button
for a manual Invoke event, as described in the topic "Invoking operations."
If the Deployment Location wizard opens after invoking an operation, complete
the steps below. (Note that if you have more than one module in your test
configuration, the Deployment Location wizard will be preceded by a different
deployment wizard that asks you to select a specific server for each module.)
In the Deployment Location wizard, WebSphere Process
Server v6.0 always appears as a selectable deployment location.
However, if you are testing a mediation module, WebSphere ESB Server
v6.0 will also appear as a selectable deployment location in the
Deployment Location wizard. Similarly, if your module contains only Java components
or it contains J2EE components that are all unimplemented, Eclipse
1.4 JVM will appear as a selectable deployment location.
To
deploy your module:
- In the Deployment Location wizard, choose one of the following
options:
- If your module contains at least one component that is not a Java™ component
or if you want to test a set of interacting modules, ensure that WebSphere
Process Server v6.0 is selected in the Deployment location list
box. (This is the designated server for running SCA applications, BPEL business
processes, human tasks, transition tables, business rules, selectors, and
other resources. You can also use this server for running mediation flows
contained in mediation modules.)
- If your module is a mediation module, you can select WebSphere
ESB Server v6.0. (Generally, if you intend to eventually deploy
your mediation module to a WebSphere Enterprise Service Bus production server,
then WebSphere ESB Server v6.0 is a good choice. However,
if you intend to eventually deploy your mediation module to a WebSphere Process
Server production server, then you may want to select WebSphere
Process Server v6.0.)
- If your module only contains Java components and you don't want to test
a set of interacting modules, or if your module contains J2EE resources but
none of the components are implemented, you can select Eclipse
1.4 JVM. (The main advantage to choosing the Eclipse JVM is that
it starts more quickly than WebSphere® Process Server or WebSphere Enterprise
Service Bus. However, once started, the Eclipse JVM, WebSphere Process
Server, and WebSphere Enterprise Service Bus all provide similar test performance.)
- In the Mode drop-down list, select either Run or Debug to
start the server in Run or Debug mode. (If the server is already running in
one of these modes, the Mode drop-down list will show
the current server mode and it will be disabled.)
- If you want to use the selected server or JVM as your default deployment
location for future testing, select the Use this as the default
and do not ask again check box. The next time that you open the
test client to invoke an operation for the same module in the same test configuration,
your module will automatically be deployed to the default deployment location
without the Deployment Location wizard opening. (If you later want to select
a different deployment location for the same module in the same test configuration,
follow the instructions in the topic "Changing deployment location properties.")
- Click Finish. If you selected a server as
your deployment location and J2EE security is enabled for that server, a User
Login dialog is displayed (if you are not already logged in) and you must
log in by completing the following steps:
- In the User ID field, type a J2EE security
user ID.
- In the Password field, type the password
for the user ID.
- Click OK. The module is deployed to your
selected deployment location and the invocation of your operation continues.
Note that each login session is associated with a single test configuration
that is identified in the title bar of the User Login dialog. The login session
endures until you manually log out by clicking the Logout button
on the Configurations page of the test client or until you are automatically
logged out when you stop or close the test client.
If the test pauses at a manual Emulate event when you have finished
deploying your module, specify some output parameter values or select an exception
to throw as described in the topic "Specifying emulation values." If the test
does not pause at a manual Emulate event, it will most likely run to completion
and you will probably want to reinvoke the operation or generate an Invoke
event to invoke and test a different operation. These tasks are described
in the topics "Reinvoking operations" and "Generating Invoke events."