Migrating the Business Space V7.0.x database and data
Before you begin
To migrate Business Space data to V8.5.7, you must use the same LDAP that you used for the previous version.
Procedure
- To migrate the Business Space data, copy
the migration folder under the folder_of_extracted_monitor_models\BusinessSpace directory
that contains the migration2002to3001.properties file. This folder was generated
by the MonitorModelMigration command
when you migrated the monitor models.
Copy the migration folder under the snapshot_folder\BusinessSpace directory to the node_profile directory. The node_profile directory is the directory of the custom node profile in the target environment where Business Space was deployed. If there is more than one custom node, you must copy the folder to each custom node profile.
- Run the preMigrateBusinessSpace700.sql script.
- Log in to the database server as a user with read and write access on the database.
- Connect to the database.
- Locate the preMigrateBusinessSpace700.sql script for your database in the profile for the cluster that you most recently configured. The script is under target_deployment_manager_profile_root\dbscripts\BusinessSpace\cluster_name\database_type\database_name.
- Save the script to a location on the same system with the database.
- Change to the directory where you copied the script, and run the preMigrateBusinessSpace700.sql script, as described in the header of the file.
- On the deployment manager, run the upgradeBSpaceSchema
command.
- Locate the command upgradeBSpaceSchema.bat in install_root\BusinessSpace\scripts.
- Run the command with the following syntax:
WhereupgradeBSpaceSchema.bat -profileName dmgr -clusterName cluster
- dmgr is the name of the deployment manager profile
- cluster is the name of the cluster where Business Space is deployed, usually the application cluster
- Migrate the Business Space schema.
- Log in to the database server as a user with read and write access on the database.
- Connect to the database.
- Locate the migrateBusinessSpaceSchema700.sql script for your database in the profile that you most recently configured, and save the script to a location on the same system with the database. The script is under target_deployment_manager_profile_root\dbscripts\BusinessSpace\cluster_name\database_type\database_name.
- Run the migrateBusinessSpaceSchema700.sql script, as described in the header of the file.
- Before running the migrateBSpaceData commands in the next step, you must
change the default security configuration of Business Space. After running
migrateBSpaceData, you will restore the previous setting.
- In the administrative console, go to Users and Groups > Manage Groups. Create an administrative group, such as administrators.
- Set the VMM administrative group name by going to Resources > Resource environment providers. Click Mashups_ConfigService > Custom properties > com.ibm.mashups.adminGroupName and provide the name of the group that you just created.
- From Users and Groups > Manage Groups, click the group that you created, go to the Members tab, and add the user who will run the migrateBSpaceData commands as a member of the group.
- Restart the environment to enable the security changes. For instructions, see Starting and stopping your environment.
- Migrate the Business Space data.
- Restart the cluster. Depending on your environment, use one of the following
procedures:
- If the Business Space database being
updated belongs to a non-clustered managed node where Business Space is configured:Start the server on the node using the startServer command from the profile_root\bin directory of the migration target server. Use the following syntax:
See startServer command in the WebSphere® Application Server documentation.startServer.bat server_name
- If the Business Space database being
updated belongs to a clustered environment:Start the deployment manager, node, and all servers using the startManager, startNode, and startServer commands from the profile_root\bin directory of the migration target server. Use the following syntax:
See startManager command, startNode command, and startServer command in the WebSphere Application Server documentation.startManager.bat startNode.bat startServer.bat server_name (start all servers on the node in sequence)
Note: You can ignore any messages about not being able to connect to the messaging engine. - If the Business Space database being
updated belongs to a non-clustered managed node where Business Space is configured:
- Check the oobLoadedStatus.properties file to confirm that the following
three values exist and are false:
importTemplates.txt=false importSpaces.txt=false importThemes.txt=false
This file is in the following location: install_root\profiles\your_node_profile_name\BusinessSpace\cluster_name\mm.runtime.prof\public\oobLoadedStatus.properties on all nodes. Not all nodes have all three of the values.
If any of these values are not set, importing the system artifacts for Business Space is still in progress. Wait until the import is complete. You can check the SystemOut.log on the node that the target server was started on to see if there are any exceptions. The log is in install_root\profiles\your_node_profile_name\logs\target_server_name\SystemOut.log.
- On the node that the target server was started on, run
the migrateBSpaceData script using the -dbcopy option
to copy Business Space data from V7.0.x to V8.5.7. In a
clustered environment, run the script on any managed node where Business
Space is deployed.
The script is in install_root\BusinessSpace\scripts\.
Use the following syntax:
where:migrateBSpaceData.bat -host host_name -port SOAP_port_number -user user_name -password password -dbcopy
- host_name is the Business Space server host name.
- SOAP_port_number is the Business Space server port number.
- user_name is the Business Space administrative user name.
- password is the password of the Business Space administrative user name.
migrateBSpaceData.bat -host local_host -port 8880 -user admin -password admin -dbcopy
Note: If you receive an SSL Signer Exchange Prompt message while running this command, click Y to add the signer to the truststore.See migrateBSpaceData command-line utility. - Stop the servers, node, and deployment manager in the
target cluster. Repeat this step for each server in the cluster. Use the stopServer, stopNode, and stopManager commands from the profile_root\bin directory on the migration source target. Use the following syntax:
stopServer.bat server_name -username user_name -password password (stop all servers on the node in sequence) StopNode.bat StopManager.bat
If the profile has security enabled, the user name provided must be a member of the operator or administrator role. If the profile does not have security enabled, the -username and -password parameters are unnecessary.
See stopServer command, stopNode command, and stopManager command in the WebSphere Application Server documentation.
- Modify the oobLoadedStatus.properties file that you checked in step 5b.
Set the following three values to true:
importTemplates.txt=true importSpaces.txt=true importThemes.txt=true
This file is in the following location: install_root\profiles\your_node_profile_name\BusinessSpace\cluster_name\mm.runtime.prof\public\oobLoadedStatus.properties.
- Start the cluster in the target environment. Depending
on your environment, use one of the following procedures:
- If the Business Space database being
updated belongs to a non-clustered managed node where Business Space is configured:Start the server on the node using the startServer command from the profile_root\bin directory of the migration target server. Use the following syntax:
See startServer command in the WebSphere Application Server documentation.startServer.bat server_name
- If the Business Space database being
updated belongs to a clustered environment:Start the deployment manager, node, and all servers using the startManager, startNode, and startServer commands from the profile_root\bin directory of the migration target server. Use the following syntax:
See startManager command, startNode command, and startServer command in the WebSphere Application Server documentation.startManager.bat startNode.bat startServer.bat server_name (start all servers on the node in sequence)
- If the Business Space database being
updated belongs to a non-clustered managed node where Business Space is configured:
- Check the oobLoadedStatus.properties file that you checked in step 5b.
Confirm that the following three values have been set to false:
importTemplates.txt=false importSpaces.txt=false importThemes.txt=false
This file is in the following location: install_root\profiles\your_node_profile_name\BusinessSpace\cluster_name\mm.runtime.prof\public\oobLoadedStatus.properties.
If any of these values are not set to false, importing the data for Business Space is still in progress. Wait until the import is complete before proceeding.
- On the node that the target server was started on, run
the migrateBSpaceData script using the -dbupgrade option
to upgrade Business Space data from V7.0.x to V8.5.7. In a
clustered environment, run the script on any managed node where Business
Space is deployed.
The script is in install_root\BusinessSpace\scripts\.
Use the following syntax:
where:migrateBSpaceData.bat -host host_name -port SOAP_port_number -user user_name -password password -dbupgrade
- host_name is the Business Space server host name.
- SOAP_port_number is the Business Space server port number.
- user_name is the Business Space administrative user name.
- password is the password of the Business Space administrative user name.
See migrateBSpaceData command-line utility.migrateBSpaceData.bat -host local_host -port 8880 -user admin -password admin -dbupgrade
- Restart the cluster. Depending on your environment, use one of the following
procedures:
- Restore the previous security configuration of Business Space.
- In the administrative console, go to Resources > Resource environment providers. Click Mashups_ConfigService > Custom properties > com.ibm.mashups.adminGroupName and restore the previous group name. The default group name is com.ibm.mashups.J2EERole.Admin.
- Restart the environment to enable the security changes. For instructions, see Starting and stopping your environment.
- Verify that the previous steps are all successful by checking the migration traces and logs.
- Stop the servers, node, and deployment
manager in the target cluster. Repeat this step for each server in
the cluster. Use the stopServer, stopNode, and stopManager commands from the profile_root\bin directory on the migration source target. Use the following syntax:
stopServer.bat server_name -username user_name -password password (stop all servers on the node in sequence) StopNode.bat StopManager.bat
If the profile has security enabled, the user name provided must be a member of the operator or administrator role. If the profile does not have security enabled, the -username and -password parameters are unnecessary.
See stopServer command, stopNode command, and stopManager command in the WebSphere Application Server documentation.
- Remove the temporary database tables by running
the postMigrateBusinessSpace700.sql script.
- Log in to the database server as a user with read and write access on the database.
- Connect to the database.
- Locate the postMigrateBusinessSpace700.sql script for your database in the profile that you most recently configured, and save it to a location on the same system with the database. The script is under target_deployment_manager_profile_root\dbscripts\BusinessSpace\cluster_name\database_type\database_name.
- Change to the directory where you copied the script, and run the postMigrateBusinessSpace700.sql script, as described in the header of the file.
Note: You might receive the following message while running data migration:
To resolve this error, modify the com.ibm.SOAP.requestTimeout property by editing the soap.client.props file that is in theproperties subdirectory of the profile_root directory. Change the com.ibm.SOAP.requestTimeout value from 180 to a larger value, such as 1800, which is 30 minutes.SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed out; target Exception=java.net.SocketTimeoutException: Read timed out.
What to do next
If you have an IBM Forms Server configured with WebSphere Process Server in the earlier releases, you must manually deploy the BSpaceForms.ear after the migration. Deploy the BSpaceForms.ear from the WASHome\installableApps\BusinessSpace directory to the application server.
If you migrated the Business Space database data from V7.0 to V8.0.1 and imported a V7.0 page (or a V7.0 space that contains a V7.0 page) into Business Space V8.0.1, the wiring between the following IBM Business Monitor widgets is lost: Instances widget and Diagrams widget. If you had those two widgets on the same page, you must wire them together manually, using the V8.0.1 event names: Instance Selected for the published event name and Show Instance for the handled event name.