How to install a stand-alone installation in IBM BPM 8.5 (Part 1)

I use the environment Linux - Oracle in the main, but, I think, the same way in others environments.

BTW I never use a "standard" installation, but "custom" only because it is more flexible and as a result, saves a lot of time. It is my first rule of an installation WAS/BPM.
At first, in 8.5 you can install BPM stand-alone in Express edition only.
1. Install the BPM's binary files using Installation Manager. It is usual way, I need not stop here.

2. You cannot use PMT for stand-alone profile, you have to use BPMConfig.sh command for this.

2.1. Before create the properties' file. You can use someone from the folder <WAS_HOME>/BPM/samples/config/express/
I chose Express-PC-Standalone-Oracle.properties and edited it (you can use my file with your settings):

##############################################
# Deployment environment basic properties.   #
##############################################
bpm.de.name=BPMEXP
# Options: true, false If this is set false, database tables are created during deployment environment creation when BPMConfig is run with the create de action . If set to true, the tables need to be created manually.
bpm.de.deferSchemaCreation=true
# Type of product configuration: Express, Standard, Advanced or AdvancedOnly
bpm.de.type=Express
# Type of deployment environment: Process Center or Process Server
bpm.de.environment=Process Center
################################################################
# Deployment environment administrator authentication alias.   #
################################################################
bpm.de.authenticationAlias.1.name=DeAdminAlias
bpm.de.authenticationAlias.1.user=wasadmin
bpm.de.authenticationAlias.1.password=wasadmin
#############################################################
# Database user authentication alias for common database.   #
#############################################################
bpm.de.authenticationAlias.2.name=BPM_DB_CMN_ALIAS
bpm.de.authenticationAlias.2.user=EXPCMNDB
bpm.de.authenticationAlias.2.password=Password
#####################################################################
# Database user authentication alias for process server database.   #
#####################################################################
bpm.de.authenticationAlias.3.name=BPM_DB_PS_ALIAS
bpm.de.authenticationAlias.3.user=EXPBPMDB
bpm.de.authenticationAlias.3.password=Password
#################################################################################
# Database user authentication alias for performance data warehouse database.   #
#################################################################################
bpm.de.authenticationAlias.4.name=BPM_DB_PDW_ALIAS
bpm.de.authenticationAlias.4.user=EXPPDWDB
bpm.de.authenticationAlias.4.password=Password
####################################################################################
# Deployment Environment Administrator role and authentication alias association   #
####################################################################################
# bpm.de.roleMapping.DeAdmin.name
bpm.de.roleMapping.1.name=DeAdmin
bpm.de.roleMapping.1.alias=DeAdminAlias
#####################
# Cell properties   #
#####################
bpm.cell.name=PCCellExp
####################################################
# Cell (WAS) administration authentication alias   #
####################################################
bpm.cell.authenticationAlias.1.name=CellAdminAlias
bpm.cell.authenticationAlias.1.user=admin
bpm.cell.authenticationAlias.1.password=admin
####################################################
# Cell role and authentication alias association   #
####################################################
# Role mapping names are pre-defined. Do not modify this value. Specify the user name in the authentication alias corresponding to this role.
bpm.cell.roleMapping.1.name=CellAdmin
bpm.cell.roleMapping.1.alias=CellAdminAlias
##############################
# Properties for each node   #
##############################
bpm.de.node.1.name=Node1
# If the hostname is the same as deployment manager, this node will be created on the same computer. Do not use localhost for environments that are spread across multiple machines.
bpm.de.node.1.hostname=server
bpm.de.node.1.installPath=/opt/ibm/BPM85Exp
bpm.de.node.1.profileName=ProcCtr01
bpm.de.node.1.initialPortAssignment=
bpm.de.node.1.server.db=ProcessServerDb,SharedDb,PerformanceDb
#########################
# Database properties   #
#########################
# Keyword to use to  refer to this set of database properties. This is not the database name.
bpm.de.db.1.name=SharedDb
# List of components that are configured on this database. For Advanced configurations the options are: Messaging, BusinessSpace, CommonDB, BPC and CellScopedDB. For Standard and Express configurations, the options are: Messaging, BusinessSpace, ProcessServer, EmbeddedECM and PDW.
bpm.de.db.1.dbCapabilities=Messaging,BusinessSpace
# Database name.
bpm.de.db.1.databaseName=BPM8
# Database type. Options: DB2, DB2zOS, Oracle or SQLServer
bpm.de.db.1.type=Oracle
# Database hostname. Do not use localhost for environments that are spread across multiple machines.
bpm.de.db.1.hostname=server
bpm.de.db.1.portNumber=1521
bpm.de.db.1.sqlServerWinAuth=false
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.1.roleMapping.1.name=DbUser
bpm.de.db.1.roleMapping.1.alias=BPM_DB_CMN_ALIAS
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.1.roleMapping.2.name=DbUserXAR
bpm.de.db.1.roleMapping.2.alias=BPM_DB_CMN_ALIAS
bpm.de.db.1.schema=EXPCMNDB
#########################
# Database properties   #
#########################
# Keyword to use to  refer to this set of database properties. This is not the database name.
bpm.de.db.2.name=ProcessServerDb
# List of components that are configured on this database. For Advanced configurations the options are: Messaging, BusinessSpace, CommonDB, BPC and CellScopedDB. For Standard and Express configurations, the options are: Messaging, BusinessSpace, ProcessServer, EmbeddedECM and PDW.
bpm.de.db.2.dbCapabilities=ProcessServer,EmbeddedECM
# Database name.
bpm.de.db.2.databaseName=BPM8
# Database type. Options: DB2, DB2zOS, Oracle or SQLServer
bpm.de.db.2.type=Oracle
# Database hostname. Do not use localhost for environments that are spread across multiple machines.
bpm.de.db.2.hostname=server
bpm.de.db.2.portNumber=1521
bpm.de.db.2.sqlServerWinAuth=false
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.2.roleMapping.1.name=DbUser
bpm.de.db.2.roleMapping.1.alias=BPM_DB_PS_ALIAS
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.2.roleMapping.2.name=DbUserXAR
bpm.de.db.2.roleMapping.2.alias=BPM_DB_PS_ALIAS
bpm.de.db.2.schema=EXPBPMDB
#########################
# Database properties   #
#########################
# Keyword to use to  refer to this set of database properties. This is not the database name.
bpm.de.db.3.name=PerformanceDb
# List of components that are configured on this database. For Advanced configurations the options are: Messaging, BusinessSpace, CommonDB, BPC and CellScopedDB. For Standard and Express configurations, the options are: Messaging, BusinessSpace, ProcessServer, EmbeddedECM and PDW.
bpm.de.db.3.dbCapabilities=PDW
# Database name.
bpm.de.db.3.databaseName=BPM8
# Database type. Options: DB2, DB2zOS, Oracle or SQLServer
bpm.de.db.3.type=Oracle
# Database hostname. Do not use localhost for environments that are spread across multiple machines.
bpm.de.db.3.hostname=server
bpm.de.db.3.portNumber=1521
bpm.de.db.3.sqlServerWinAuth=false
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.3.roleMapping.1.name=DbUser
bpm.de.db.3.roleMapping.1.alias=BPM_DB_PDW_ALIAS
########################################################
# Database role and authentication alias association   #
########################################################
# Role mapping names are pre-defined. Do not modify this value. Specify the user name in the authentication alias corresponding to this role.
bpm.de.db.3.roleMapping.2.name=DbUserXAR
bpm.de.db.3.roleMapping.2.alias=BPM_DB_PDW_ALIAS
bpm.de.db.3.schema=EXPPDWDB

My second rule is: I never create DB and DB's objects during profile creation.
The reason - if you get some error with DB, you have to delete the profile and have to create it again. Save your time. I choose the parameter bpm.de.deferSchemaCreation=true (do you remember -dbCreateNew false -dbDelayConfig true manageprofiles' properties?)

2.2. Run BPMConfig.sh using your properties' file.

[root@server bin]# ./BPMConfig.sh -create -de Express-PC-Standalone-Oracle.properties
Logging to file /opt/ibm/BPM85Exp/logs/config/BPMConfig_20131216-112402.log.
Validating the profile registry.
[]
Configuring stand-alone profile.
Creating stand-alone profile.
INSTCONFSUCCESS: Success: Profile ProcCtr01 now exists. Please consult /opt/ibm/BPM85Exp/profiles/ProcCtr01/logs/AboutThisProfile.txt for more information about this profile.
Generating SQL files.
Provisioning cell.
Configuring the cell.
XL TXE-J compiling stylesheet: null
XL TXE-J compiling stylesheet: null
XL TXE-J compiling stylesheet: null
XL TXE-J compiling stylesheet: null
Provisioning deployment environment.
Generating database configuration files to /opt/ibm/BPM85Exp/profiles/ProcCtr01/dbscripts/BPMEXP.
Performing security configuration.
Configuring data sources.
Configuring the database(s).
Operation completed successfully
The HTTP and HTTPS ports are added to the virtual hosts list.
Configuring the node.
Configuring the REST services end points.
Saving configuration changes, please be patient...
BPMConfig completed successfully.

3. Create the script for Oracle users creating:

CREATE USER EXPCMNDB IDENTIFIED BY Password;
grant connect, resource, unlimited tablespace to EXPCMNDB;
grant create view to EXPCMNDB;
grant javauserpriv to EXPCMNDB;
grant execute on dbms_lock to EXPCMNDB;
CREATE USER EXPBPMDB IDENTIFIED BY Password;
grant connect, resource, unlimited tablespace to EXPBPMDB;
grant create view to EXPBPMDB;
grant javauserpriv to EXPBPMDB;
grant execute on dbms_lock to EXPBPMDB;
CREATE USER EXPPDWDB IDENTIFIED BY Password;
grant connect, resource, unlimited tablespace to EXPPDWDB;
grant create view to EXPPDWDB;
grant javauserpriv to EXPPDWDB;
grant execute on dbms_lock to EXPPDWDB;

4. Execute this script and all the others from /dbscripts in this order:

/dbscripts/BPMEXP/Oracle/BPM8/EXPCMNDB/createSchema_Express.sql
/dbscripts/BPMEXP/Oracle/BPM8/EXPCMNDB/createSchema_Messaging.sql
/dbscripts/BPMEXP/Oracle/BPM8/EXPBPMDB/createSchema_Express.sql
/dbscripts/BPMEXP/Oracle/BPM8/EXPBPMDB/createProcedure_Express.sql
/dbscripts/BPMEXP/Oracle/BPM8/EXPPDWDB/createSchema_Express.sql

5. Run bootstrapProcessServerData as usual (from <Profile_HOME>/bin):

[root@server bin]# ./bootstrapProcessServerData.sh
Bootstraping data for server at /opt/ibm/BPM85Exp/profiles/ProcCtr01
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
importFile: /opt/ibm/BPM85Exp/BPM/Lombardi/imports/system-toolkit.twx
deploy: false
latestSystemToolkit: true
activateSnapshot: false
importFile: /opt/ibm/BPM85Exp/BPM/Lombardi/imports/system-coaches.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/ibm/BPM85Exp/BPM/Lombardi/imports/system-dashboards.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/ibm/BPM85Exp/BPM/Lombardi/imports/governance-toolkit.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/ibm/BPM85Exp/BPM/Lombardi/imports/content-integration-toolkit.twx
deploy: false
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/ibm/BPM85Exp/BPM/Lombardi/imports/process-portal.twx
deploy: true
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/ibm/BPM85Exp/BPM/Lombardi/imports/saved-search-admin.twx
deploy: true
latestSystemToolkit: false
activateSnapshot: false
importFile: /opt/ibm/BPM85Exp/BPM/Lombardi/imports/standard-hiring-sample.twx
deploy: true
latestSystemToolkit: false
activateSnapshot: false
'BootstrapProcessServerData admin command completed.....'

6. At last

[root@server bin]# ./startServer.sh server1
ADMU0116I: Tool information is being logged in file
           /opt/ibm/BPM85Exp/profiles/ProcCtr01/logs/server1/startServer.log
ADMU0128I: Starting tool with the ProcCtr01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 26890

That all.