When you create a stand-alone profile,
database scripts are generated, which you can use to configure the Business Space tables for
dashboards. You can choose to run these scripts manually. In a network
deployment environment, the Business Space database scripts
are generated when you create the deployment environment, and they
must be run manually.
This task is relevant only if
you choose to delay the execution of the scripts while creating a
stand-alone profile or if you are configuring a network deployment
environment.
Before you begin
- For a stand-alone server, create a profile either by running the
Profile Management Tool or the manageprofiles command.
- For a network deployment environment, create the deployment environment
by using the monConfig script and corresponding monConfig properties
file.
- 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.
- Make sure that your application server with Business Space is stopped.
If you are using DB2® for z/OS® and
the required resources have not already been set up as part of the
core product installation, complete the following additional items
before you begin this task:
- Create a TEMP database and a TEMP table space to contain the declared
temporary tables for processing scrollable cursors.
- Create a dedicated storage group to contain the Business Space data.
About this task
If you used the manageprofiles command-line
utility to create a stand-alone profile, and are using Oracle or SQL
Server on the stand-alone server, you must create the database manually
instead of using the -dbCreateNew parameter.
If you are using a remote database or using DB2 for z/OS, you must
also create the database manually.
In a network deployment environment,
run the database scripts before you start the clusters and cluster
members.
The configBusinessSpaceDB script
that is generated for DB2, Oracle,
and SQL Server 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_BusinessSpace script
with your product instead of the configBusinessSpaceDB script.
Important: Business Space tables must be created in a table
space with a page size of 32K. If the default table space does not
have a page size of 32K, the tables are not created.
Procedure
To configure the database tables for Business Space,
complete the following steps:
- Make sure that you are using a user ID with sufficient
authority to create tables.
- If required, edit the Business Space database scripts
as follows:
- Go to the location where the scripts were generated. These scripts are stored in the following location:
- Stand-alone server: monitor_root/profiles/profile_name/dbscripts/BusinessSpace/node_name_server_name/database_type/database_name
- Deployment manager node: monitor_root/profiles/profile_name/dbscripts/BusinessSpace/cluster_name/database_type/database_name
Where:
- profile_name is the name of the stand-alone
or deployment manager profile.
- node_name is the node on which the profile
is created.
- server_name is the stand-alone server name.
- cluster_name is the name of the cluster where Business Space is deployed.
- database_type identifies the database product.
- database_name denotes the name of the database
where the tables will be created.
- For DB2 for z/OS, edit the createTablespace_BusinessSpace.sql and createTable_BusinessSpace.sql scripts
to update them with your storage group and schema details:
- createTablespace_BusinessSpace.sql and createTable_BusinessSpace.sql:
Replace the STOGROUP value with the name of the storage group that
you are using on your MVS system.
- createTable_BusinessSpace.sql: Optionally
specify a different schema name other than the default value of IBMBUSSP.
- If you are configuring a remote database, copy the directory
that contains all the generated (and edited) Business Space scripts to
a directory on your database server.
- On the computer that hosts your database server, open a
command prompt and run one of the following commands, based on your
operating system. Your user ID must have access to the
command-line interpreter for the database type and have permission
to run commands.
- For DB2, Oracle, and
SQL Server, run this command:
configBusinessSpaceDB.sh
configBusinessSpaceDB.bat
For DB2 and SQL Server,
use the optional -createDB parameter if you want
to create a different database instead of using the existing database.
Tip: 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 does 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 these files in the following
order:
- createTablespace_BusinessSpace.sql
- createTable_BusinessSpace.sql
- If you changed the default IBMBUSSP schema
name in the Business Space database
scripts to another value, you must also make this change in the WebSphere® Application
Server administrative
console and in one of the Business Space configuration
files:
- Log on to the administrative console. Go to . On the Configuration tab, update
the schema name in the Value field. Be sure
to include a period (.) at the end of the schema name.
- Update the value for schemaName in
the config-bspace.xml file. Do not add a period
at the end of the schema name. This file is located in
the following directory:
- Stand-alone server: monitor_root/profiles/profile_name/config/cells/cell_name/nodes/node_name/servers/server_name/config-bspace.xml
- Deployment manager node: monitor_root/profiles/profile_name/config/cells/cell_name/clusters/cluster_name/config-bspace.xml
- Restart the environment.
- 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 Updating templates and spaces after installing or updating widgets.
What to do next
Important: If your product database is an Oracle
database, the
Business Space component
is configured with the Profile Management Tool or the
manageprofiles command-line
utility to use the same database, with the default schema IBMBUSSP,
and the default password that you enter during profile creation. If
you want to use a different password for the IBMBUSSP user name, you
must use the administrative console to update 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.
Update the endpoints for widgets that you want to be
available in Business Space.
Before
using dashboards, set up security that you need to use with the Business Space component and
the widgets that your team is using.
Tip: The
Business 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. For more information, see
Changing the timeout settings for the Business Space Ajax proxy.