Use the repotools utility to put the version 1.0 schema
to an XML file and then transfer the data from the XML file to the
version 4.0 schema.
About this task
You can transfer the version 1.0 database to an XML file
and then load from the XML file into a version 4.0 database. You can
also use this method to move from one database management system to
another; for example, move from an Apache Derby database to an IBM® DB2® database.
Procedure
This procedure works across every operating system that
the connector supports. The paths and commands in the procedure depend
on the installation root directories and the operating systems. The
repotools utility can be found at C:\Program Files\IBM\SapConnector\server\repotools.bat.
- Install Rational® Connector
for SAP Solution Manager 4.0 on the same system where Rational Connector for SAP Solution Manager
1.0 is installed.
- Shut down Rational Connector
1.0.
- Go to the server directory under the Rational Connector 4.0 installation root
directory.
% c:
% cd \Program Files\IBM\SapConnector\server
- Set the SAPC_HOME environment variable
to point to the Rational Connector
1.0 server/conf installation root directory.
% set SAPC_HOME=c:\Program Files (x86)\IBM\SapConnector\server\conf
- Put the contents of the Rational Connector 1.0 database to a temporary
file.
% repotools dump -file c:\temp\conn1.0db.xml
-fromSchema 1.0
- Reset the SAPC_HOME environment variable
to point to the Rational Connector
4.0 server/conf installation root directory.
% set SAPC_HOME=c:\Program Files\IBM\SapConnector\server\conf
- Load the Rational Connector
1.0 schema XML file to a Rational Connector
4.0 database.
% repotools load -file c:\temp\conn1.0db.xml
-fromSchema 1.0
Important: It
was discovered that in some rare cases, a transaction, and a report
with the same name, existing in Solution Manager on the same Blueprint
node, can generate the same ID in the Rational tools. The Rational Connector now generates IDs in
a new unique way in 4.0. Simply pushing a blueprint generates new
IDs, which can result in duplicate artifacts that are created in the Rational tools. In cases where Delete
Unused Rational Artifacts is selected, old artifacts are
deleted from the Rational tools.
If you want to prevent this behavior, you can enable a new ignoreObjectGUID
option.
- Before you restart the Rational Connector
server, consider adding the following option to your JAVA_OPTS environment
variable found in server.startup. You can find
the server.startup file in the same directory
as repotools.
-Dcom.ibm.rational.sap.ignoreObjectGUID="true"
This option ensures that the same user
IDs used in the 1.0 Rational Connector
are used for SAP Test Objects discovered during blueprint pushes.