Converting an IBM® DB2® Universal Database administrative repository from local to remote
 Technote (FAQ)
 
Problem
Moving your IBM DB2 administrative repository from the local host to a remote database server.
 
Cause
Need to move DB2 repository to database server on another host.
 
Solution
Steps to perform before connecting the administrative server to a new DB2 database on a remote server:
  1. Create backup of the local DB2 repository database using XMLconfig export:
    $WAS_HOME/bin/xmlconfig -export filename.xml -adminNodeName nodename

    In V4.0, the node name in the xml file used by xmlconfig -import, must be the same case as the hostname of the server. For example, if "Host1" is in the xml file and the hostname is "host1", modify the xml file, otherwise, the administrative console will show two nodes, "host1" and "Host1".

    In case of multiple nodes sharing the same repository database, stop the application server on all of the nodes. If the $WAS_HOME/etc/secbootstrap file exists, delete it.

    Also verify that
    com.ibm.CORBA.securityEnabled=false
    is set in $WAS_HOME/properties/sas.server.props for all nodes.
  2. Stop WebSphere Application Server services.
  3. Create a new administrative repository on the new remote DB2 database server.
    1. WebSphere Application Server connects to a DB2 repository database server using the DB2 client, regardless of whether the database is local or remote. However,
      • For a local repository, configure the database name, database user, and password in $WAS_HOME/bin/admin.config.
      • For a remote repository, use a database alias name, database user, and password. It is also necessary to catalog the remote node and the database on the node, using the following commands on the system running WebSphere Application Server:

        db2 catalog tcpip node <nodename> remote <ipaddress> server <port>

        where,
        nodename = local alias for the node being cataloged
        ipaddress = remote server ip address or fully qualified hostname
        port = DB2 listener port (default is 50000); check services file

        db2 catalog db <dbname> as <alias> at node <nodename>

        where,
        dbname = name of remote database to access
        alias = name in admin.config
    2. Include the following changes in $WAS_HOME/bin/admin.config:
      install.initial.config=true
      com.ibm.ejs.sm.adminServer.initializeDb=true
      com.ibm.ejs.sm.adminServer.createTables=true
      com.ibm.ejs.sm.adminServer.dbdatabaseName=<alias>
      com.ibm.ejs.sm.adminServer.dbuser=db2inst1
      com.ibm.ejs.sm.adminServer.dbpassword=<new password>
    3. Save the changes to the admin.config file and start the administrative server
    4. To avoid creating a default server, set
      install.initial.config=false
      in admin.config.
  4. Import the XMLConfig file using

    $WAS_HOME/bin/xmlconfig -export filename.xml -adminNodeName nodename
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Data & Information Management DB2 Connect
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 1160388
IBM Group: Software Group
Modified date: Feb 10, 2004