Migrating Systems Director Database from Apache Derby to SQL 2005 (Remote)

I’ve previously detailed the steps to migrate Systems Director’s default Apache database to a local instance of SQL Server 2005.  I’ve also tested the steps to migrate Apache to a remote SQL Server 2005 instance below.   My Systems Director Server is running on Windows Server 2008 R2 (64 bit).

If you login to your Director Server and select Manage – IBM Systems Director Server you should see that Apache is the current database.

To migrate to a remote instance of Microsoft SQL Server 2005, follow these instructions:

1)  Ensure that the pre-requisite software is installed on the ISD server:

  • Microsoft SQL Server JDBC Driver 3.0
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server 2005 Command Line Query Utility

You can download these components from Microsoft’s web sites.  I’ve stored the versions I used here.  I found I had to logoff/logon again so the SQL command line tool would be found in the steps below.

2)  Stop the IBM Systems Director Service.

3) On your SQL server, create a database for Director, for example IBMSystemsDirectorDB and an associated owner account.  I called mine SystemsDirectorDBUser

Note that I’ve unticked the enforce password policy and expiration.

4) Edit the following file C:\Program Files\IBM\Director\proddata\cfgdbcmd.rsp  and comment out the Apache section and update the SQL database section.  I’ve attached a copy of my cfgdbcmd.rsp file here.  The password isn’t shown in my file (put in your own) and this is encrypted in the next step anyhow.

5) Encrypt the password in the cfgdbcmd.rsp via the following command:  C:\Program Files\IBM\Director\bin cfgserver.bat –db

6) Enter the IBMSystemsDirectorDB user id/password when prompted

The output when I ran this command is here

7) Change to the C:\Program Files\IBM\Director\bin directory

8 ) Run the following command:  cfgdbcmd.cmd

The output when I ran this command is here

9) Change to the C:\Program Files\IBM\Director\bin directory

10) Run the following command:  smreset  (select 1 if prompted)

11) Start the IBM System Director Service (it may take up to 20-30 minutes to be fully initialised)

When you login to your Director Server again and select Manage – IBM Systems Director Server you should see that SQL is the current database.

Your work is done !

Advertisements
  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: