IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced > Install IBM BPM Advanced > On Windows > Network deployment environment > Configure profiles and create an ND environment > Create an ND environment > Use the administrative console > 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 component and registering REST endpoints on the administrative console

You can install the Business Space component using the administrative console.

Before you begin this task, you must :

• Install the product software and created a profile. When install your product, Business Space files are included with the installation for the profiles that you set up. Your profile is not configured for Process Portal until you explicitly configure the Business Space component on the profile.

• Configure Business Process Choreographer for IBM BPM runtime environments that need the Human Task Management widgets. For more information, see "Configuring Business Process Choreographer" in the IBM BPM documentation.
• Enable security, if you want to set up a secured environment for Process Portal.

• Configure Representational State Transfer (REST) services. If you have a stand-alone server environment or you are using the Deployment Environment wizard to configure your runtime environment, the REST service endpoints are configured and enabled automatically. For other environments, use the REST services administrative console page to configure the REST services. If you want widgets to be available in Process Portal, configure the REST services for those widgets. On the Business Space Configuration administrative console page, you register the REST endpoints so that Business Space associates widgets with the endpoints and the widgets appear in the palette for use.

• If you want to configure the Business Space component on a server or cluster using a different data source than the product data source: Create the data source in the server or cluster scope with the correct JNDI name of jdbc/mashupDS before configuring the Business Space component using the administrative console.

• For Oracle, to use a different schema for the Business Space database tables than the one used by the product database to create a data source manually before you open the Business Space Configuration page:

  1. Create the schema using the database product software.

  2. Use the administrative console to configure the JDBC provider.

  3. Use the administrative console to create a data source with the JNDI name of jdbc/mashupDS at the server or cluster scope, depending on your environment.

  4. Use the administrative console to create an authentication alias. Set the user name to the schema you created and set the authentication according to your Oracle setup.
  5. Set the authentication alias on the data source.

If you are using deployment environments or other advanced profile configuration, use the administrative console to configure the Business Space component to work with Process Portal in your runtime environment.

Procedure

1. Ensure that the administrative console is running.

2. In the navigation pane click Servers > Server Types > WebSphere application servers or Servers > Clusters > WebSphere application server clusters.

3. Select the name of your server or cluster target.

4. On the Configuration page, under Business Integration, click Business Space Configuration. The Business Space Configuration page opens. If Business Space has already been configured, you can view this page, but you cannot edit the fields.

5. Select the Install Business Space service check box.

6. In the Database schema name box, type the name of the database schema that you want to use for the Business Space database.

   In Oracle, the schema is the same as the user name set on the authentication alias on the data source.

7. If no data source is designated in the Existing Business Space data source field, go to Create Business Space data source using and select a data source that connects to the database you want to use with Business Space.

   Designating a data source under Create Business Space data source using: creates a data source for Business Space with a JNDI name of jdbc/mashupDS that is modeled on the data source you selected.

   The Business Space data source is created on the server or cluster on which you are configuring Business Space, even if the product data source is on a different server or cluster.

   If you do not see an existing data source that you want to use, you must cancel the Business Space Configuration page, set up the database and the data source that you want to use, and then restart the Business Space Configuration page to complete the configuration. See the Before you begin section.

8. Click OK.

9. To register the proper deployment target (cluster or server) for the system REST endpoints for each of the widgets you are using in Business Space, click REST service endpoint registration.

   The target that you select for a REST service endpoint type can set the scope of the data displayed in some widgets. Or, you might want to select a particular cluster or server for better performance or availability.

   If you are using Human Task Management widgets, you can select more than one REST service provider for a server or a cluster in the row for the Process Services and Task Services types. Select the provider with Name=Federated REST Services, the provider with Name=Business Process Choreographer REST services, or the provider with Name=BPD engine REST services. If you have tasks and processes running in both Business Process Choreographer and the business process definition (BPD) engine, select the federated REST services. If you are using only processes and tasks that are running in the Business Process Choreographer (modeled in Integration Designer), select the Business Process Choreographer REST services. If you are using only processes and tasks that are running in the BPD engine (modeled in Process Designer), select the BPD engine.

   If you do not specify the target, the REST endpoint of this type is not registered with Business Space, and any widgets that need the REST service endpoint of this type will not be visible in Business Space.

10. Save the configuration.

11. Run the scripts to configure the Business Space database tables before starting the deployment environment or the clusters. The scripts were generated when you completed the configuration. For more information, see Configuring the Business Space database: .

What to do next

If you are using Oracle, the password of the authentication alias of the Business Space data source is set to same as the Business Space schema name. The default value of the schema is IBMBUSSP. When you configure the Business Space component, you can specify a different schema on the administrative console or in the command line. In that case, the default password is the same as the schema you specify. If you want to use a different password for the Business Space user name, use the administrative console to updated JDBC Resources: Find the data source jdbc/mashupsDS. Modify the value of the authentication alias to make it match the password of the Business Space schema name. Save your changes and restart the server.

Tip: TheBusiness Space component uses a proxy component to connect to your REST services. In some cases, if REST services are not responsive, you must update the connection timeout settings to your REST services, depending on the performance of the REST service servers. See Changing the timeout settings for the Business Space Ajax proxy: .

Configure the Business Space component for ND environments

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

Related information:

Java 2 Connector authentication data entry settings
Configure a JDBC provider and data source