InfoCenter Home >
3: Migration overview >
3.5: Switching administrative databases >
3.5.2: Settings to change when switching administrative databases

3.5.2: Settings to change when switching administrative databases

The following steps describe the settings modified by the database conversion assistant. It is highly recommended that you use the database conversion assistant to switch database settings, rather than editing the settings by hand.

Note, the following example steps pertain specifically to switching from an Instant DB database to a DB2 database. Again, they are provided as a reference to what the assistant is doing. Use the assistant to modify the settings.

  1. Modify the administrative server configuration file, changing entries as follows:
    • From:
      com.ibm.ejs.sm.adminServer.dbDriver=jdbc.idbDriver
      To:
      com.ibm.ejs.sm.adminServer.dbDriver=COM.ibm.db2.jdbc.app.DB2Driver
    • From:
      com.ibm.ejs.sm.adminServer.dbUser=
      To:
      com.ibm.ejs.sm.adminServer.dbUser=db2admin
      where db2admin is the appropriate database user name.
    • From:
      com.ibm.ejs.sm.adminServer.dbPassword=
      To:
      com.ibm.ejs.sm.adminServer.dbPassword=db2admin
      where db2admin is the appropriate database password.
    • From:
      com.ibm.ejs.sm.adminServer.dbUrl=jdbc:idb:c:/WebSphere/AppServer/bin/was.prp
      To:
      com.ibm.ejs.sm.adminServer.dbUrl=jdbc:db2:was
    • Modify the entry that points to the database driver:
      com.ibm.ejs.sm.adminserver.classpath
      For example, change from:
      c:/WebSphere/AppServer/lib/idb.jar
      To:
      c:/SQLLIB/java12/db2java.zip
    •   The remainder of this step is specific to migration from Instant DB to DB2. The migration assistant does not perform the following changes, even in the case of Instant DB to DB2 migration.

    • Locate the entry:
      com.ibm.ejs.sm.util.process.Nanny.path
      and add an entry for the database installation root, such as c:\\SQLLIB\\bin for DB2 on Windows NT.
    • Remove the entries:
      com.ibm.ejs.sm.adminServer.connectionPoolSize=1
      com.ibm.ejs.sm.adminServer.dbSchema=
      
  2. Modify product_installation_root/bin/setupCmdLine (setupCmdLine.sh on UNIX):
    • Change from:
      SET DB2DRIVER=c:\WebSphere\AppServer\lib\idb.jar
      To:
      SET DB2DRIVER=c:\SQLLIB\java\db2java.zip
      as appropriate for the location of the database driver.
    • Set the DB2_HOME entry:
      DB2_HOME=/home/db2inst1
      as appropriate for the installation root of the database product.
  3. Modify the administrative server startup script:
    • Change from:
      DB_TYPE=InstantDB
      To:
      DB_TYPE=DB2
    • Change from:
      DBUSERID=
      To:
      DBUSERID=db2inst1
    • Change from:
      DB_INSTANCE_HOME=
      To:
      DB_INSTANCE_HOME=/home/db2inst1
  4. Modify product_installation_root/properties/initial_setup.config:

    • Change from:
      <config-file>product_installation_root/hosts/default_host/WSsamplesIDB_app/WSsamplesIDB_app_create.xml</config-file>
      To:
      <config-file>product_installation_root/hosts/default_host/WSsamples_app/WSsamples_app_create.xml</config-file>
    • Change from:
      <value>jdbc:ibd</value>
      To:
      <value>jdbc:db2</value>
    • Change from:
      <value>product_installation_root/lib/idb.jar</value>
      To:
      <value>home/db2inst1/sqllib/java/db2java.zip</value>
    • <value>product_installation_root/bin/myidb.prp</value>
      To:
      <value>WAS</value>
      where WAS is the name of the DB2 database.
Go to previous article: Using the database conversion assistant to switch administrative databases Go to next article: Switching server databases to DB2/390: Switching administrative databases

 

 
Go to previous article: Using the database conversion assistant to switch administrative databases Go to next article: Switching server databases to DB2/390: Switching administrative databases