Monday, 17 February 2014

IBM Business Process Manager 8.5 - More about BPMConfig

From the IBM Information Centre: -


The BPMConfig command is used to create or extend a typical network deployment environment. For example, it can also be used to create the database scripts and profiles, start and stop the deployment environment, and validate the deployment environment configuration.

Syntax

BPMConfig [-create | -update | -upgrade | -validate configurationFile | -start [configurationFile] | -stop [configurationFile] | -help [actionName]]


The BPMConfig command uses a properties file to configure your environment according to the settings that you specify. Your BPM installation includes several sample configurations files that are provided as a starting point for your configuration. These sample files are composed of common properties and settings for different IBM BPM environments. Before you begin your configuration, select a sample file that most closely resembles the configuration that you want, copy the file, and customize it to suit your own environment.

And this is what happened when I used BPMConfig to create my first Deployment Environment: -

/opt/IBM/WebSphere/AppServer/bin/BPMConfig.sh -create -de Advanced-PC-SingleCluster-DB2.properties

Logging to file /opt/IBM/WebSphere/AppServer/logs/config/BPMConfig_20140214-150812.log.
Validating the profile registry.
[]
Configuring the deployment manager.
The deployment manager profile already exists at /opt/IBM/WebSphere/AppServer/profiles/Dmgr01.
Starting deployment manager profile Dmgr01.
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 21149
Configuring managed node profiles.
A managed node profile already exists at /opt/IBM/WebSphere/AppServer/profiles/AppSrv01.
Retrieving signers.
CWPKI0308I: Adding signer alias "CN=rhel6.uk.ibm.com, OU=Root Ce" to local
keystore "ClientDefaultTrustStore" with the following SHA digest:
FC:FF:4A:AD:1C:56:34:3F:C5:A8:0F:39:5E:06:6C:F9:54:CF:5B:33
Adding the node AppSrv01Node to the cell bpm85Cell.
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
CWPKI0309I: All signers from remote keystore already exist in local keystore.
ADMU0001I: Begin federation of node AppSrv01Node with Deployment Manager at
rhel6.uk.ibm.com:8879.
ADMU0009I: Successfully connected to Deployment Manager Server:
rhel6.uk.ibm.com:8879
ADMU0507I: No servers found in configuration under:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/localhostNode01Cell/nodes/AppSrv01Node/servers
ADMU2010I: Stopping all server processes for node AppSrv01Node
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: AppSrv01Node
ADMU0014I: Adding node AppSrv01Node configuration to cell: bpm85Cell
ADMU0016I: Synchronizing configuration between node and cell.


ADMU0300I: The node AppSrv01Node was successfully added to the bpm85Cell cell.


ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone bpm85Cell configuration
have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the bpm85Cell Deployment Manager with
values from the old cell-level documents.


ADMU0306I: Note:
ADMU0304I: Because -includeapps was not specified, applications installed on
the standalone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the bpm85Cell cell using wsadmin $AdminApp
or the Administrative Console.


ADMU0003I: Node AppSrv01Node has been successfully federated.
Generating SQL files.
Provisioning cell.
Generating database configuration files to /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/bpm85Cell.
Configuring the databases.
Configuring the cell.
Configuring the deployment manager.
Provisioning deployment environment.
Generating database configuration files to /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/dbscripts/De1.
Performing security configuration.
Creating clusters.
Configuring data sources.
Configuring the databases.
Configuring clusters.
Operation completed successfully
Provisioning managed node AppSrv01Node.
The HTTP and HTTPS ports are added to the virtual hosts list.
Configuring the node.
Creating cluster members.
3
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/system-toolkit.twx
deploy: false
latestSystemToolkit: true
activateSnapshot: false
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/system-coaches.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/system-dashboards.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/governance-toolkit.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/content-integration-toolkit.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/ssi4bpm-guided-workflow.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/process-portal.twx
deploy: true
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/saved-search-admin.twx
deploy: true
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/standard-hiring-sample.twx
deploy: true
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/advanced-hiring-sample.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/IBM/WebSphere/AppServer/BPM/Lombardi/imports/procurement-sample.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
Configuring the REST services end points.
Saving configuration changes...
Synchronizing node AppSrv01Node.
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/syncNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0401I: Begin syncNode operation for node AppSrv01Node with Deployment
Manager rhel6.uk.ibm.com: 8879
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node AppSrv01Node has been synchronized with
Deployment Manager rhel6.uk.ibm.com: 8879
Stopping deployment manager profile Dmgr01.
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/stopServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server dmgr stop completed.

The 'BPMConfig.sh -create -de Advanced-PC-SingleCluster-DB2.properties' command completed successfully.

No comments: