IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Testing modules > Unit testing > Running unit tests in the test client > Testing interface operations

Deploying modules from the integration test client

When you start an operation, the integration test client detects whether your module must 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 must have started an operation by clicking the Continue icon for a manual Invoke event, as described in the topic "Invoking operations."

If the Deployment Location wizard opens after invoking an operation.

In the Deployment Location wizard, IBM Process Server always appears as a selectable deployment location. However, if you are testing a mediation module, WebSphere Enterprise Service Bus Server will also appear as a selectable deployment location in the Deployment Location wizard. Similarly, if your module contains only Java components or it contains Java 2 Platform Enterprise Edition components that are all unimplemented, Eclipse JVM will appear as a selectable deployment location. If you are testing a module that is deployed as part of a process application or a toolkit, IBM Process Center Server appears as a selectable deployment location.

To deploy your module:


Procedure

  1. If you have selected more than one module for testing or you have more than one module in your test configuration, the Select Deployment Location for Each Module page of the Deployment Location wizard opens and you should complete one of the following steps:

    • If you want to use the default deployment location specified for each module listed in the wizard, click Finish to immediately deploy the modules. (If administrative security is enabled for one or more of the servers, you will first need to specify a user ID and password as described in the final step of this topic.)

    • If you want to change the default deployment location specified for one or more modules, select the check box beside each module for which you want to specify a different deployment location and then click Select Location. The Select Deployment Location page of the Deployment wizard opens and you can work with it by completing the following steps.

  2. In the Select Deployment Location page of 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 IBM BPM 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 deployed as part of a process application or a toolkit, ensure that IBM Process Center Server is selected as the deployment location. If there are multiple modules in the process application or toolkit, all the modules will be tested.

    • If your module is a mediation module, you can select WebSphere Enterprise Service Bus Server. (Generally, if you intend to eventually deploy your mediation module to a WebSphere Enterprise Service Bus production server, then WebSphere Enterprise Service Bus Server is a good choice. However, if you intend to eventually deploy your mediation module to an IBM Process Server production server, then you may want to select IBM BPM.)

    • If your module only contains Java components and you do not want to test a set of interacting modules, or if your module contains Java 2 Platform Enterprise Edition resources but none of the components are implemented, you can select Eclipse JVM. (The main advantage to choosing the Eclipse JVM is that it starts more quickly than IBM BPM or WebSphere Enterprise Service Bus. However, once started, the Eclipse JVM, IBM BPM, and WebSphere Enterprise Service Bus all provide similar test performance.)

  3. 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.)

  4. 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 start 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 properties").

  5. Click Finish. If you selected a server as your deployment location and administrative security is enabled for that server, a User Login window is displayed (if you are not already logged in) and you must log in by completing the following steps:

    1. In the User ID field, type an administrative security user ID. The default user ID is admin.

    2. In the Password field, type the password for the user ID. The default password is also admin.

    3. Click OK. The module is deployed to your selected deployment location and the invocation of your operation continues.
    If that each login session is associated with a single test configuration that is identified in the title bar of the User Login window. 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 an exception is received that states that the server must be running in development mode, you can enable development mode for the server by following the instructions in the topic Enabling development mode for stand-alone test environment servers.


What to do next

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 start and test a different operation. These tasks are described in the topics "Reinvoking operations" and "Generating Invoke events."

Testing interface operations