Deploy modules to the test environment

In IBM Integration Designer, 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.


Create a server in the test environment

If you chose to install the Process Server test environment profile when you installed IBM Integration Designer, then you will already have a default test environment server. However, if you deleted the default server or if you are working with a standalone installation of Process Server, create a environment server for testing your modules.

Create an IBM Business Process Manager profile before creating your test servers.

To create a server:

  1. In the Business Integration or Debug perspective, click the Servers tab to open the Servers view.

  2. In the Servers view, right-click anywhere in the view and select New > Server. The New Server wizard opens to the Define a New Server page.

  3. In the Select the server type list box, select one Process Server.

  4. In the Server's host name field, ensure the correct host name is selected for the server to create. By default, the host name localhost (IP address 127.0.0.1) is automatically selected, which is the appropriate selection if you chose to install the test environment when you installed IBM Integration Designer. However, you can also type or select another fully-qualified DNS name or IP address if you chose to install standalone Process Server on a different machine than IBM Integration Designer.

    Only if you have installed a local test environment with IBM Business Monitor on WebSphere Application Server can you target a remote server with IBM Business Monitor running on WebSphere Application Server.

  5. Click Next. The Server Settings page opens.

  6. Edit the settings as required. You can obtain help information for any individual field or control by selecting a field or control and pressing F1.

  7. Click Next again. The Add and Remove Projects page opens.

  8. On the Add and Remove Projects page, select one or more modules to add to the server. Information about adding modules to a server is found in the topic "Adding modules to servers."

  9. Click Finish. The new server is now displayed in the Servers view.



Create servers for process applications

In IBM Integration Designer, you can create a new server to test your modules in a process application or toolkit. The server can run in either a Network Deployment (ND) or non-ND environment. There are two types of servers that you can create in Integration Designer to work with process applications:

If you are developing a process application that resides in a Process Center, you generally run and test the process application on a Process Center server.

However, when you have finished developing and testing the application, you need to install the process application on a process server that resides outside the authoring environment of the Process Center. This external process server is called a Process Server on Process Center, which can be a development server, test server, staging server, or production server environment.

Information about creating a Process Center server or a Process Server on Process Center is found in the following topics:



Create an IBM Process Center server

An IBM Process Center server (also known as a playback server) is used to run process applications on an IBM Process Center. When you import a process application into IBM Integration Designer from the Process Center, a Process Center server is automatically created in the Servers view. For this reason, there is generally no need to manually create a Process Center server unless the existing server has been deleted.

Integration Designer automatically detects any connected Process Center and creates and displays a Process Center server for each Process Center in the Servers view. All process applications and toolkits are displayed under their associated Process Center servers. If you add or remove a Process Center connection, the Servers view is automatically updated to add or remove the associated server and the workspace is automatically updated to reflect the new state of the process applications and toolkits.

If you are connected to a Process Center but there is no corresponding Process Center server in the Servers view, you can create a server by completing the instructions in the following procedure.

In order to successfully publish or deploy from Integration Designer to a Process Center server, the version of both tools must be exactly the same.

  1. Ensure the Process Center is running.
  2. In Integration Designer, click the Servers tab to open the Servers view.

  3. In the Servers view, right-click anywhere in the view and select New > Server. The New Server wizard opens to the Define a New Server page.
  4. Define the new Process Center server by completing the following steps:

    1. In the Select the server type list box, select IBM Process Center.

    2. In the Server's host name field, ensure the correct host name is specified for the Process Center server (playback server) to create.

      Only if you have installed a local test environment with IBM Business Monitor on WebSphere Application Server can you target a remote server with IBM Business Monitor running on WebSphere Application Server.

    3. In the Server name field, accept the default name or type in another name for the server.

    4. Click Next.

  5. Set the connection settings for the Process Center by completing the following steps:

    1. To set the host name, HTTP port, user ID, and password with the Process Center URI settings, click Use Default Process Center. (To view or change the Process Center URI settings, select Window > Preferences to open the Preferences window, then expand Business Integration in the tree view and select Process Center.)

    2. In the Host name field, specify the host name of the Process Center to which you want to connect.

    3. In the HTTP port field, specify the port of the Process Center.

    4. In the User ID and Password fields, specify the user name and password to use to log into the Process Center.

    5. To create attempt to establish a connection to the Process Center to verify that your connection settings are correct, click Test Connection.

    6. Click Next.

  6. If the Process Center is not a member of a network deployment (ND) environment, specify the connection settings for the Process Center server by completing the following steps:

    1. In the Host name field, specify the host name to use for the Process Center server.

    2. In the RMI port field, specify the ORB bootstrap connector port to use to connect to the Process Center server.

    3. In the SOAP port field, specify the SOAP connector port to use to connect to the Process Center server.

    4. Select the Security is enabled on this server check box to specify the Process Center server has security enabled. (The check box is selected by default.)

    5. In the User ID and Password fields, specify the administrative user ID and password to use to log into the Process Center server. (By default, the fields are pre-populated with the user ID and password that are used to log into the Process Center.)

    6. Click Finish.

  7. If your server is a member of a network deployment (ND) environment, the correct host name and ports are automatically determined and set, but you must specify the remaining connection settings for the Process Center server by completing the following steps:

    1. Select the Security is enabled on this server check box to specify the server has security enabled. (The check box is selected by default.)

    2. In the User ID and Password fields, specify the user ID and password that are used to log into the ND deployment manager. (By default, the fields are pre-populated with the user ID and password that are used to log into the Process Center.)

    3. Click Finish.

The new Process Center server is displayed in the Servers view. Any process application or toolkits residing in the workspace and that are installed on the server are shown nested under the server.



Create an Process Server on IBM Process Center

An Process Server on IBM Process Center is used to run process applications on a Process Server that is connected to a Process Center. The server created can be a development server, staging server, test server, or production server.

If you have a Process Center server in the Servers view of IBM Integration Designer, you will find that it is easier and faster to create a Process Server on Process Center by following the instructions in the topic "Connecting to a process server". However, if you do not have a Process Center server in the Servers view, you can create a Process Server on Process Center by completing the instructions in the following procedure.

  1. In IBM Integration Designer, click the Servers tab to open the Servers view.

  2. Ensure the Process Server is running.

  3. In the Servers view, right-click anywhere in the view and select New > Server. The New Server wizard opens to the Define a New Server page.
  4. Define the new Process Server on Process Center by completing the following steps:

    1. In the Select the server type list box, select Process Server on Process Center.

    2. In the Server's host name field, ensure the correct host name is selected for the new Process Server on Process Center to create.

      Only if you have installed a local test environment with IBM Business Monitor on WebSphere Application Server can you target a remote server with IBM Business Monitor running on WebSphere Application Server.

    3. In the Server name field, accept the default name or type in another name for the server.

    4. Click Next.

  5. Set the connection settings for the Process Center by completing the following steps:

    1. To set the host name, HTTP port, user ID, and password with the Process Center URI settings, click Use Default Process Center. (To view or change the Process Center URI settings, select Window > Preferences to open the Preferences window, then expand Business Integration in the tree view and select Process Center.)

    2. In the Host name field, specify the host name of the Process Center to which you want to connect.

    3. In the HTTP port field, specify the port of the Process Center.

    4. In the User ID and Password fields, specify the user name and password to use to log into the Process Center.

    5. To create attempt to establish a connection to the Process Center to verify that your connection settings are correct, click Test Connection.

    6. Click Next to select the kind of Process Server on Process Center to create.

  6. In the Servers list, select the process server to create in the workspace for the Process Center. The list can display the names of one or more development, staging, test, or production process servers, but it only displays the names of the process servers that are currently connected to the Process Center that you specified on the previous page of the wizard.

  7. Click Next.

  8. If your selected process server is not a member of a network deployment (ND) environment, specify the connection settings for the Process Server by completing the following steps:

    1. In the Host name field, specify the host name of the IBM Process Center.

    2. In the RMI port field, specify the ORB bootstrap connector port to use to connect to the server.

    3. In the SOAP port field, specify the SOAP connector port to use to connect to the server.

    4. Select the Security is enabled on this server check box to specify the server has security enabled. (The check box is selected by default.)

    5. In the User ID and Password fields, specify the administrative user ID and password to use to log into the server. (By default, the fields are pre-populated with the user ID and password that are used to log into the Process Center.)

    6. Click Finish.

  9. If your server is a member of a network deployment (ND) environment, the correct host name and ports are automatically determined and set, but you must specify the remaining connection settings for the Process Server by completing the following steps:

    1. Select the Security is enabled on this server check box to specify the server has security enabled. (The check box is selected by default.)

    2. In the User ID and Password fields, specify the user ID and password that are used to log into the ND deployment manager. (By default, the fields are pre-populated with the user ID and password that are used to log into the Process Center.)

    3. Click Finish.

The new Process Server on Process Center is displayed in the Servers view. Any process application snapshots residing in the workspace and that are installed on the server are shown nested under the server.

Unlike a Process Center server, publishing is not available to a Process Server on Process Center because the snapshot must be installed on a Process Server using the Process Center. Also, you cannot make changes to a snapshot, which means there is never a need to publish.



Connect to a process server

If you have an IBM Process Center server in the Servers view of IBM Integration Designer, you can connect to a process server to quickly and easily create an Process Server on Process Center in the Servers view. A Process Server on Process Center is used to run process applications on a Process Server that is connected to a Process Center. Note: In order to successfully publish or deploy from Integration Designer to a Process Center server, the version of both tools must be exactly the same. Complete the instructions in the following procedure to connect to a process server and create a Process Server on Process Center.

  1. In IBM Integration Designer, click the Servers tab to open the Servers view.

  2. Ensure the Process Server is running.

  3. In the Servers view, right-click the Process Center server and select Connect to a Process Server. The New Server wizard opens.

  4. In the Servers list, select the process server to create in the workspace for the Process Center. The list can display the names of one or more development, staging, test, or production process servers, but it only displays the names of the process servers that are currently connected to the Process Center that you specified on the previous page of the wizard.

  5. Click Next.

  6. If your selected process server is not a member of a network deployment (ND) environment, specify the connection settings for the Process Server by completing the following steps:

    1. In the Host name field, specify the host name of the IBM Process Center.

    2. In the RMI port field, specify the ORB bootstrap connector port to use to connect to the server.

    3. In the SOAP port field, specify the SOAP connector port to use to connect to the server.

    4. Select the Security is enabled on this server check box to specify the server has security enabled. (The check box is selected by default.)

    5. In the User ID and Password fields, specify the administrative user ID and password to use to log into the server. (By default, the fields are pre-populated with the user ID and password that are used to log into the Process Center.)

    6. Click Finish.

  7. If your server is a member of a network deployment (ND) environment, the correct host name and ports are automatically determined and set, but you must specify the remaining connection settings for the Process Server by completing the following steps:

    1. Select the Security is enabled on this server check box to specify the server has security enabled. (The check box is selected by default.)

    2. In the User ID and Password fields, specify the user ID and password that are used to log into the ND deployment manager. (By default, the fields are pre-populated with the user ID and password that are used to log into the Process Center.)

    3. Click Finish.

The new Process Server on Process Center is displayed in the Servers view. Any process application snapshots residing in the workspace and that are installed on the server are shown nested under the server.

Unlike a Process Center server, publishing is not available to a Process Server on Process Center because the snapshot must be installed on a Process Server using the Process Center. Also, you cannot make changes to a snapshot, which means there is never a need to publish.



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 IBM Integration Designer server configuration editor and then edit some basic settings, such as modifying a port number. Modifying port numbers, for example, avoids creating additional server profiles.

Generally, to change a property in the server administrative console that is also found in the server configuration editor, you may need to change the property in the administrative console first and then make the corresponding change in the server configuration editor. This is dependent on the specific property to change.

If you are specifically interested in editing server security settings, you should read the topic "Managing security" and its related subtopics.

To edit server configurations:

  1. To edit properties in the server administrative console:

    1. In the Business Integration or Debug perspective, click the Servers tab to open the Servers view.

    2. In the Servers view, right-click your running server and select Administration > Run administrative console. The administrative console opens.

    3. In the User ID and Password fields, specify your administrative user ID and password and then click Log In. (The default user ID and password is admin unless you chose to change the default user ID and password when you installed IBM Integration Designer using IBM Installation Manager.)

    4. Edit the server configuration as required. You can obtain help information for any individual field or control in the administrative console by selecting a field or control and pressing F1.

      Save changes and close the administrative console.

    5. If the server is already running and you want the server to pick up your changes to the server configuration, right-click the server and select Restart. (Additional information about restarting a server is found in the topic "Restarting servers.")

  2. To edit properties in the server configuration editor:

    1. In the Business Integration or Debug perspective, click the Servers tab to open the Servers view.

    2. In the Servers view, right-click your server and select Open. The server configuration editor opens.

    3. Edit the server configuration as required. You can obtain help information for any individual field or control in the server configuration editor by selecting a field or control and pressing F1.
    4. Press Ctrl+S to save your changes and close the editor.

    5. If the server is already running and you want the server to pick up your changes to the server configuration, right-click the server and select Restart. (Additional information about restarting a server is found in the topic "Restarting servers.")



Enable development mode for stand-alone test environment servers

When a test environment server is installed as part of the BPM installation, the server is automatically set to run in development mode by default. This is the mode for a test environment server. However, if you install a stand-alone server separately from your IBM Business Process Manager installation and you want to use the stand-alone server as a test environment server, you need to manually enable the server to run in development mode.

When development mode is enabled on a stand-alone server, it is possible to republish, stop, or uninstall business process applications even when the application has running instances of business processes or human tasks. This is an important capability that is generally required for all test environment servers. (However, if you have a stand-alone server to use as a production environment rather than as a test environment, the server should generally not run in development mode, which protects your long-running instances from being accidentally stopped or uninstalled.)

To enable development mode in a stand-alone test environment server:

  1. In the Servers view of IBM Integration Designer, right-click your running stand-alone test environment server and select Administration > Run Administrative Console. The login page opens.

  2. In the User ID and Password fields, type the user ID and password and click Log in.

  3. In the navigation tree of the administrative console, expand Servers and Server Types.

  4. Select the WebSphere application servers link. The Application Servers page opens.

  5. Click the server link. (By default, the server is named server1.) The server page opens.

  6. Select the Run in development mode check box and save your changes.
  7. Close the administrative console and restart your stand-alone test environment server.



Start servers in the test environment

Before you can create a running instance of a component in IBM Integration Designer, start the server.

If you have not yet added your modules to a server, you should add them by following the instructions in the topic "Adding modules to test environment servers."

To start a server:

  1. In the Business Integration or Debug perspective, click the Servers tab to open the Servers view.

  2. In the Servers view, right-click your server and select one of the following server modes from the menu:

    • Debug

    • Start

    These two modes are the most common means of starting a server in IBM Integration Designer.

    These options are disabled for remote Process Center Servers.

  3. In the Servers view, ensure the Status area displays one of the following status messages before you continue with the development activities:

    • Debugging

    • Started



Add 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.

Throughout the course of the development activities, EAR projects are generated for your modules. It is these EAR projects that you actually add to the servers and run rather than the modules they represent. However, in IBM Integration Designer, business integration modules are the key resource and users are largely shielded from Java 2 Platform Enterprise Edition resources like EAR projects. For this reason, the deployment documentation generically refers to adding, running, and removing modules on servers.

To add modules to servers:

  1. In the Business Integration or Debug perspective, click the Servers tab to open the Servers view.

  2. In the Servers view, right-click your server and select Add and Remove Projects. The Add and Remove Projects wizard opens. In the Available Projects list box, the EAR projects are displayed that correspond to your modules.

  3. Complete one of the following steps:

    • To add a single module to the server, then select the corresponding EAR project in the Available Projects list box and click Add. The EAR project is added to the Configured Projects list box.

    • To add all modules to the server, then click Add All. All of the available EAR projects that correspond to your modules are added to the Configured Projects list box.

  4. Click Finish. The selected EAR projects are added to the server.



View the state and status of modules or servers

You can view the state of a module that you have added to a test environment server, or the state of a server that is connected to your workspace, using the Servers view. In IBM Integration Designer, you can deploy your modules to one or more servers in the test environment. The Servers view displays a list of all your servers and projects that are associated with that server. A project displays under a server when a project from the workbench is added to the server. You can use the Servers view to determine the current status and state of the server; and the projects and modules added to the server, including process applications or toolkits that contain the modules.

If you add or remove servers from your test environment, the Servers view is automatically updated to reflect the current state and status of the servers, including any process applications or toolkits that are in your workspace. Disconnecting from a server removes it from the Servers view.

  1. In the Business Integration perspective, click the Servers tab to open the Servers view.
  2. The Servers view shows each Process Server or Process Center Server that is connected to your workspace. The Servers view also displays the current state of all connected servers. Information about the state and status of the server is displayed next to the server name.

    • Server state

      The following table lists the possible states of the server:

      Description of the server states

      Server state Description
      Start A connection to the server is being established, or the actual server is starting.
      Started The server is started. Both the workspace and the server are ready to run applications on the server.
      Stop The server is stopping. The workspace is in the process of connecting to the server and is ending the process on the server.
      Stopped The server is in a stopped state, or a connection cannot be established between your workspace and the server.

    • Server status

      The following table lists the possible server status:

      Description of the server status

      Server status Description
      Synchronized All the modules in the workspace have been published to the server. The server and the applications are in sync.
      Publishing Changes to the modules in the workspace are being published to the server. Files related to the modules are in the correct location for the server to find and use them.
      Republish At least one module in the workspace has changed. The module needs to be published to the server.

  3. The Servers view also displays the state and status of modules. The modules are shown in a hierarchical tree view. If the modules are part of a process application or toolkit, the modules are displayed under the name of the process application or toolkit. Information about the state and status of a module is displayed next to the module name.

    • Module state

      The following table lists the possible states of a module:

      Description of the module states

      Module state Description
      Started The module is started on the server and is ready to run.
      Stopped The module is stopped on the server and cannot run.

    • Module status

      The following table lists the possible module status:

      Description of the module status

      Module status Description
      Synchronized The module has been published to the server. There are no pending changes to the module.
      Republish The module has changes which need to be published to the server. The server needs to be updated.

  4. The Servers view also displays the status and version of a process application or toolkit that contains modules in your workspace. Information about status and version is displayed next to the process application or toolkit name.

    • Process application or toolkit state

      Description of the process application or toolkit states

      Module state Description
      Started All modules in the process application or toolkit have started.
      Stopped Some or all of the modules in the process application or toolkit are stopped on the server and cannot run.

    • Process application or toolkit status

      The following table lists the possible status:

      Description of the process application or toolkit status

      Module status Description
      Synchronized All modules contained in the process application or toolkit have been published to the server. There are no pending changes.
      Republish At least one module contained in the process application or toolkit has changes which need to be published to the server. The server needs to be updated.



Publishing modules to test environment servers

In IBM Integration Designer, 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.

Although most types of changes to components are automatically picked up by running servers, some types of changes are not. For example, some changes to BPEL business processes may require you to publish the modules to the server. If you make modifications to a BPEL business process and you find these changes are not being picked up automatically by a running instance of your business process, then you must publish the modules. When you have deployed a module that is part of a Process Application and are testing the module on a Process Center Server, the Publish action actually performs two separate operations. First, the changed module components are delivered to the Process Center repository. Then, the modules are deployed from the repository to the Process Center Server.

To publish modules:

  1. In the Business Integration or Debug perspective, click the Servers tab to open the Servers view.

  2. In the Servers view, right-click your running server and select Publish. The modules are published to the server.

If you are experiencing communication problems with the remote server, such as problems in publishing to the remote server or obtaining the status of the server, see Resolve communication problems with remote servers for information about how to resolve these problems.



Publishing changed resources to servers

If changed (new, modified, or deleted) resources exist in your workspace and you click the Update Running Servers button in the Build Activities view, a window will open that enables you to view the resources and choose whether to publish the updates to the servers. To publish changed resources to servers:

  1. In the Business Integration perspective, click the Build Activities tab. (If the Build Activities tab is not visible, open either the Business Integration view or the Physical Resources view and click the Show Build Activities View icon .) The Build Activities view opens.

  2. If the Project status section is not yet expanded in the Build Activities view, expand it.

  3. If the Status column for a server indicates that an integration module or component test project requires republishing (because it contains new, changed, or deleted resources), click the Update Running Servers button. The View and Publish Changes to Servers window opens.

    In the Changes that will be published list, a tree view displays the new or changed workspace resources that are candidates for publishing to one or more of the supported servers displayed in the Project Status section of the Build Activities view. If the new, changed, or deleted resources occur solely in business integration modules, component test projects, or libraries, the tree view is displayed in logical mode. However, if new, changed, or deleted resources are found in Java or Java 2 Platform Enterprise Edition projects, the tree view is displayed in physical mode.

  4. To toggle the tree view between logical mode and physical mode, click the Tree Mode button .

  5. To disable the View and Publish Changes to Server window and prevent it from being displayed again, select the Do not show this window again check box. (If you choose to disable the window, you can later enable it again by following the instructions in the topic "Disabling or enabling the Publish Changes window".)

  6. Click Publish to publish all of the changed resources to the servers.

    If you notice timeout exceptions or out of memory exceptions, it might be caused by the size of your resources. See "Prevent timeout and out-of-memory exceptions during installation or deployment."



10. Remove 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 they do not needlessly impact the performance of the server.

To remove modules from servers:

  1. In the Business Integration or Debug perspective, click the Servers tab to open the Servers view.

  2. In the Servers view, right-click your server and select Add and remove projects. The Add and Remove Projects wizard opens and displays the EAR projects that correspond to your modules in the Configured Projects list box.

  3. Complete one of the following steps:

    • To remove a single module from the server, then select the corresponding EAR project in the Configured Projects list box and click Remove. The EAR project is removed from the Configured Projects list box and is added to the Available Projects list box.

    • To remove all modules from the server, then click Remove All. All of the EAR projects that correspond to your modules are removed from the Configured Projects list box and are added to the Available Projects list box.

  4. Click Finish. The selected EAR projects are removed from the server.



11. Restarting servers in the test environment

In IBM Integration Designer, 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.

To restart a server:

  1. In the Business Integration or Debug perspective, click the Servers tab to open the Servers view.

  2. In the Servers view, right-click your running server and select one of the following server modes:

    • Restartin Debug

    • Restart

    These two modes are the most common means of restarting a server in IBM Integration Designer.

  3. In the Servers view, ensure the Status area displays one of the following status messages before you continue with the development activities:

    • Debugging

    • Started



12. Stop servers in the test environment

Whenever you finish using a test environment server in IBM Integration Designer, you should stop it. This ensures the server will not unnecessarily impact the performance of other tools in the workbench or the computer that it is running on.

To stop a server:

  1. In the Business Integration or Debug perspective, click the Servers tab to open the Servers view.

  2. In the Servers view, right-click your server and select Stop.

    This option is disabled for remote Process Center Servers.

  3. In the Status area of the Servers view, ensure the status of the server is Stopped before you continue with the development activities.



13. Create or resetting default server profiles

A default server profile is a test environment server profile created when the test environment is installed with IBM Integration Designer. In the Servers view, you can choose to create or reset a default server profile. For example, you might want to create a default server profile that you earlier chose not to have created when you installed the test environment. Or you might need to reset an existing default server profile that is no longer functioning correctly.

The default server profiles require an IBM DB2 database server, which you can choose to install when you install IBM Integration Designer.

Before starting up IBM Integration Designer to create or reset a default server profile, make sure that you have permission to create and drop databases. Verify the local DB2 database server is set up correctly on your system and is started. (You can use the DB2 Control Center to check.) Make sure that you know the port number on which the database server is listening.

All the profiles that you create and reset using the instructions below will use the same local database server (instance). Verify the IBM Integration Designer environment is set up to use the same database server.

If you are using a DB2 database that was not installed as part of the IBM Integration Designer installation, make sure the database server is accessible as follows. You must complete these instructions before starting IBM Integration Designer.

You should see one of the following two results.

If that does not work, check the following:

To create or reset default server profiles:

  1. Close any command windows or Windows Explorer browsers that are open in the folder where the profile is installed. Otherwise, when the profile is deleted, the removal of the directory will fail and the test environment will not be reset.

  2. In the Business Monitoring perspective, click the Servers tab to open the Servers view.

  3. To reset a default server profile (which will delete the server profile, and then create it again), stop the server instance that references the profile. For example, to reset the Process Server server profile, stop the Process Server server instance.

  4. Click Manage Server Profiles . (Alternatively, you can right-click any server and select Manage Server Profiles.) The Manage Server Profiles window opens.

    The window displays the logical names of the default server profiles, which are the names that you see when you install the Monitor test environment. The window also displays the physical names of the default server profiles, which are the actual names that are used in a server configuration. (You can open a server configuration in the server configuration editor by double-clicking a server instance in the Servers view.) For example, Process Server is a logical name and qbpmaps is a physical name. The server instances listed in the Servers that will be deleted and Servers that will be created or recreated list boxes refer to the physical names of the default server profiles.

  5. Select the check box beside each action to initiate for the listed servers. For each action that you select, the Servers that will be deleted list displays the names of any server instances that will be deleted from the Servers view. Similarly, the Servers that will be created list displays the names of any server instances that will be created or reset in the Servers view.

  6. Click OK to begin creating or resetting the selected server profiles.

  7. If the Administrator Credentials wizard opens, specify a user ID and password for each profile name that is listed, then click Next.

  8. On the Add the Database Credentials page, you can see a list of the local databases (if they exist) that will be dropped if you reset the profile or profiles you chose. Any data in those databases will be lost. Verify the DB2 database instance is up and running, the credentials are correct, and the port number is correct (the default is 50000 but it might be different on your system).

  9. Click Finish.

Although it takes a significant amount of time to create or reset a default server profile, the operations are run as background processes and you can continue to work in the workspace. When the operations have completed, the new server instances appear in the Servers view.



+

Search Tips   |   Advanced Search