configureBusinessSpace command

Use the configureBusinessSpace command to configure the Business Space database.

This command configures the Business Space data source and generates the scripts that create and configure database tables.

After using the command, save your changes to the master configuration using one of the following commands:
  • For Jython:
    AdminConfig.save()
  • For Jacl:
    $AdminConfig save

If the application server is not running, supply the -conntype NONE option when running this command.

Required parameters

-serverName server_name
A parameter that specifies the server name for the configuration. For configuring Business Space on a server, you must specify both a serverName and a nodeName.
-nodeName node_name
A parameter that specifies the node name for the configuration. For configuring Business Space on a server, you must specify both a serverName and a nodeName.
-clusterName cluster_name
A parameter that specifies the cluster name for the configuration. For configuring Business Space on a cluster, you must specify a clusterName.

Optional parameters

-createTables true|false
Specifies if you want to create the Business Space database tables. If the value is set to true, for DB2, Oracle, or SQL Server, the database is configured with Business Space tables. Setting this parameter to true requires that the Business Space database has been created before running this command. The default value is false.
-dbName database_name
Specifies the database that you are using for Business Space. If your application server and DB2 are on same z/OS image, you must specify the -dbName parameter.
-dbWinAuth true|false
Specifies if you are using Windows Authentication with Microsoft SQL Server. If you want to use Windows Authentication in your SQL Server environment, you must specify this parameter astrue. The default is false.
-schemaName schema_name
An optional parameter that specifies the database schema for the Business Space database configuration. The default value is IBMBUSSP.
-tablespaceDir table_space_path
An optional parameter that specifies a directory path or file name prefix for the files used as the physical locations of table spaces. The default value is BSP. Valid for DB2, Oracle and SQL Server (otherwise ignored). For SQL Server, this parameter applies to the primary data file and log files.
-tablespaceNamePrefix table_space_prefix
An optional parameter that specifies a prefix string added to the beginning of table space names to make them unique. The default value is BSP. If a table space name prefix is longer than four characters, it is truncated to four characters. Valid for DB2, DB2 z/OS V8, DB2 z/OS V9, and Oracle (otherwise ignored).
-dbLocationName database_location_name
An optional parameter that specifies the database location name on z/OS®. The default value is BSP or the product database name. Valid on DB2 z/OS V8 and V9 (otherwise ignored).
-storageGroup storage_group
An optional parameter that specifies the storage group on z/OS for Business Space. If you are using z/OS, you must update the database scripts that are generated before running them. For more information about the scripts, see Configuring Business Space database tables.
-bspacedbDesign database_design_file_name
An optional parameter that specifies a database design file that you are using to define all database configuration information, including the schema, and the table space directory. If you designate a database design file using the -bspacedbDesign parameter, you do not need to designate the -schemaName, -tablespaceDir , or -storageGroup parameters, unless you want to override what is in the database design file for particular database configuration information.
Note: The JNDI name of jdbc/mashupDS is always used for a Business Space data source, so the JNDI name in the database design file is not used. If a data source with a JNDI name of jdbc/mashupDS exists, this command stops without configuring the profile unless you also specify the -replaceDatasource true parameter.
-productTypeForDatasource product_database
An optional parameter that specifies properties to use to create the data source to use with Business Space. Designating a productTypeForDatasource creates a data source for Business Space with a JNDI name of jdbc/mashupDS that is modeled on the data source of an installed product, such as IBM® Process Server, WebSphere® Enterprise Service Bus, IBM Business Monitor, and WebSphere Business Compass. Valid values are WPS (to designate IBM Business Process Manager or WebSphere Enterprise Service Bus), WPBS (to designate WebSphere Business Compass), and WBM (to designate IBM Business Monitor). If the bspacedbDesign parameter is also specified, the productTypeForDatasource overrides the database type and JDBC provider, and the JNDI name in the database design file is not used.
Note: If a data source with a JNDI name of jdbc/mashupDS exists, this command stops without configuring the profile unless you also specify the -replaceDatasource true parameter.
-replaceDatasource true|false
An optional parameter that specifies whether the configureBusinessSpace command runs if the profile has already been configured. The default value is false. When a profile is configured for Business Space, a data source with a JNDI name of jdbc/mashupDS is created. If the data source exists and you run the configureBusinessSpace command without specifying -replaceDatasource true, the command does not change the configuration. If you specify true, the command deletes the data source and its JDBC provider, creates new ones, and creates new DDL scripts.
–save true|false
A parameter that indicates saving your configuration changes. The default value is false.

Examples

The following example uses the configureBusinessSpace command to configure a Business Space data source on a server.

  • Jython example:
    AdminTask.configureBusinessSpace('[-nodeName myNode -serverName
     myServer']')
  • Jacl example:
    $AdminTask configureBusinessSpace {-nodeName myNode -serverName
     myServer}

The following example uses the configureBusinessSpace to configure a Business Space data source on a cluster and save the changes.

  • Jython example:
    AdminTask.configureBusinessSpace('[-clusterName myCluster -save
     true]')
  • Jacl example:
    $AdminTask configureBusinessSpace {-clusterName myCluster -save
     true}

The following example uses the configureBusinessSpace to configure a Business Space data source on a cluster, with a schema name and a product data source designated for IBM Process Server.

  • Jython example:
    AdminTask.configureBusinessSpace('[-clusterName myCluster
     -schemaName myCluster -productTypeForDatasource WPS -save true]')
  • Jacl example:
    $AdminTask configureBusinessSpace {-clusterName myCluster
     -schemaName myCluster -productTypeForDatasource WPS -save true}

The following example uses the configureBusinessSpace to configure a Business Space data source on a cluster using database information that is in the database design file.

  • Jython example:
    AdminTask.configureBusinessSpace('[-clusterName myCluster
     -bspacedbDesign "C:/BSpace_dbDesign.properties" -save true]')
  • Jacl example:
    $AdminTask configureBusinessSpace {-clusterName myCluster
     -bspacedbDesign "C:/BSpace_dbDesign.properties" -save true}