Modifying the IBM Process Server environment type

If you want to modify the environment type that was specified during initial configuration, update the configuration using the updateBPMConfig administrative command. The environment type indicates how IBM® Business Process Manager is used (for example, in a development, test, staging or production environment). Process authors can set environment-specific variables for each process application and then define values for each type of environment in which a process runs.

About this task

For example, load testing might be done on a test server, while a staging environment type might be used as a temporary location to host changes before putting those changes into a production environment. You might specify Staging as the environment type if the server you are configuring is accessed and used to review content and new functionality.

Valid values are as follows:

Development: Use Development if the server you are configuring is to be used as a development environment.
Test: Use Test if the server is to be used as a testing environment.
Staging: Use Staging if the server is to serve as a staging platform to be used as a preproduction server.
Production: Use Production if the server is to serve in a production capacity.

To change the environment type for a Process Server, perform the following steps.

Procedure

Stop the Process Server.
Start the wsadmin scripting tool. To start wsadmin using the Jython language, run the following command from the bin directory of the IBM BPM installation:
```
wsadmin -conntype NONE -lang jython -profileName profileName
```
For BPM Express, profileName is the name of the stand-alone profile (and may be omitted if this is the only profile). For BPM Standard and BPM Advanced, profileName is the name of the deployment manager profile.
Run the updateBPMConfig administrative command to update the environment type, as shown in the following examples:
- For a stand-alone server deployment environment, run the following command:
```
AdminTask.updateBPMConfig( [ '-nodeName', 'Node_Name', '-serverName', 'Server_Name', '-environmentType', 'Environment_Type' ] )
AdminConfig.save()
```
- For a clustered deployment environment, run the following command (where App_Cluster_Name is the name of the Application cluster in your deployment environment):
```
AdminTask.updateBPMConfig( [ '-clusterName', 'App_Cluster_Name', '-environmentType', 'Environment_Type' ] )
AdminConfig.save()
```
Start the Process Server.