IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced for z/OS: Process Server > Configure IBM BPM Advanced for z/OS: Process Server > Configure components > Configure additional components > Configure Process Portal > Configure the Business Space component for Process Portal > Configure the Business Space component for ND environments

Configure the Business Space database

You can manually install database tables for Business Space on a remote database server with scripts that are generated by the installation program. If you are using a deployment environment, or if your database is remote, install these tables after configuring Business Space.

Before you complete this task, :

• Install the product.

• Create profiles and configure servers or clusters for Business Space.

• For Oracle: create the database.

• For Microsoft SQL Server: set SQL Server instance authentication. The SQL Server JDBC driver supports mixed authentication mode only. Therefore, when the SQL Server instance is created, the authentication must be set to SQL Server and Windows.

• For all databases, make sure that the database is installed using a UTF-8 Universal character set if you want to use Business Space in your environment.
• Verify that your application server with Business Space is stopped.

If you are using DB2 V9.x, and you would like performance improvements, edit the createTablespace_BusinessSpace.sql file. The createTablespace_BusinessSpace.sql file is available in profile_root/dbscripts/BusinessSpace/ node_name_ server_name/ database_type/ database_name for a stand-alone server, or profile_root/dbscripts/BusinessSpace/ cluster_name/ database_type/ database_name for a cluster.

• Change IMMEDIATE SIZE 8000 PAGESIZE 32K to IMMEDIATE SIZE 8000 AUTOMATIC PAGESIZE 32K.

• Add the line PREFETCHSIZE AUTOMATIC after EXTENTSIZE 16 under both CREATE SYSTEM TEMPORARY TABLESPACE @TSDIR@TMPTP and CREATE REGULAR TABLESPACE @TSDIR@REGTP.

The configBusinessSpaceDB script sets up tables for Business Space with a specific database. (If you want to create tables on an existing database other than the specific one, use the createDBTables script with your product instead of the configBusinessSpaceDB script.)

Procedure

To configure the database tables for Business Space:

1. Verify that you are using a user ID with sufficient authority to create tables.
2. Locate the script in the profile you most recently configured, and save it to a location on the same system with the database.

   • For all databases except DB2 for z/OS, locate the configBusinessSpaceDB.bat or configBusinessSpaceDB.sh script.

   • For DB2 for z/OS, if you want to configure the Business Space database tables with all other database objects, run the Business Space files individually. Locate createTablespace_BusinessSpace.sql and createTable_BusinessSpace.sql.

   By default, the scripts are located in the following directory: profile_root/dbscripts/BusinessSpace/ node_name_ server_name/ database_type/ database_name for a stand-alone server, or profile_root/dbscripts/BusinessSpace/ cluster_name/ database_type/ database_name for a cluster. The updated scripts (with the information entered during profile creation) are located in the profile for the server or cluster that you most recently configured. If you used the Deployment Environment Configuration wizard, the scripts are located in the dmgr profile. When you configure a remote database, copy the scripts from the system where your product is installed to a place on the remote system.

3. Open a command prompt and run one of the following commands, based on your operating system.

   Copy the folder with the batch files and scripts to the same location as your database and run the command there. Your user ID must have access to the command-line interpreter for the database type and have permission to run commands.

   • configBusinessSpaceDB.sh

   For DB2 and SQL Server, use the optional -createDB parameter if you want to create a different database instead of using the existing database.

   When using SQL Server, you see the following warning statements in the systemout.log file after running the database script: ... Warning! The maximum key length is 900 bytes .... If you are using the federated repositories as a user registry, you can ignore the warnings. If you are using the stand-alone LDAP registry, ensure that the number of characters in all the user distinguished name (DN) entries in your organization do not exceed the 131 character limit. If the number of characters in any of the user DN entries exceeds 131 characters, you must change the user account registry to the federated repositories option.

   For DB2 for z/OS, run the following files in order:

   • createTablespace_BusinessSpace.sql
   • createTable_BusinessSpace.sql

4. For DB2 and DB2 for z/OS , bind the command-line interface to the Business Space database using the following commands:
   • db2 connect to database_name
   • db2 bind DB2_installation_directory\bnd\@db2cli.lst blocking all grant public
   • db2 connect reset

   where:

   • database_name is the name of the Business Space database
   • DB2_installation_directory is the directory where DB2 is installed

5. If you are creating the Business Space database again, after it had been previously deleted, you must import the Business Space templates and spaces before you can use the Business Space environment. Complete the steps at Update Business Space templates and spaces after installing or updating widgets.

What to do next

• Update the endpoints for widgets that you want to be available in Business Space.
• Set up security for Business Space and the widgets that your team is using.

Configure the Business Space component for ND environments

Related tasks:
Configure the Business Space component for Process Portal
Configure the Business Space component using PMT
Configure the Business Space component and registering REST endpoints on the administrative console
Configure REST services for a server, cluster, or component
Enabling widgets for cross-cell environments
Enabling widgets to work with multiple endpoints
Configure REST services in a service provider
Configure the Business Space component using the command line
Registering widget REST service endpoints using the command line

Related reference:
configureBusinessSpace command