Knowledgebase

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Pointing the Administration Server to a Different Database

In the event of an unplanned database failure in a development environment, it may be desirable to point the Administration Server to a different database — referred to in this document as the ‘target’ database. This can be done by modifying information in a number of Administration Server files. These instructions are found in the following sections.

 

Requirements

The instructions in this section assume that the ALES schema is installed on the target database and that the target database is the same database product (for example, Oracle 10).

 

Instructions

  1. Make sure the target database has the ALES schema installed.
  2. Modify the necessary Administration Server files as described in Table 12-1.

    3. Table 12-1 Changes to Administration Server Files
    File
    Property
    Description
    ales32_admin\config\
    database.properties
    ConnectionURL
    Change the JDBC connection string to the target database in the following format:
    jdbc:oracle:thin:@<host>:<port>:<sid>
    <host>— name/IP of the database machine
    <port>—database listener port number
    <sid>—database SID
    Example:
    javax.jdo.option.ConnectionURL: jdbc:oracle:thin:@acmedb.acme.com:1521:orcl
    ConnectionUserName
    If necessary, change the name of the OES database user in the target database.
    Note: Not necessary if the target database uses the same database username (default = admin).
    Example: javax.jdo.option.ConnectionUserName: admin
    ConnectionPassword
    Add the following line after the ConnectionUserName entry:
    javax.jdo.option.ConnectionPasssord: <dbuser_password>
    where <dbuser_password> is the password of the OES db user in the target database (default = password).
    Notes:
    • The existing file does not contain this line.
    • These instructions are for development environments so the password may be stored in clear text if local security policy permits. If not, use the following procedure to encrypt the password and specify the encrypted value.
    a. Define the ConnectionPassword value with the clear text password and complete this procedure through step 3 to ensure that the server starts.
    b. Use asipassword to encrypt the password.
    c. Once the server starts, login to the asi console and reset the DatabaseAuthenticator with the new password.
    d. Remove the clear text password from database.properties.
    e. Continue the parent procedure from step 4.
    ales32_admin\config\
    admin_install.properties
    db.login
    If necessary, change the name of the OES database user in the target database.
    Note: Not necessary if the target database uses the same username for the OES database user (default = admin).
    Example: db.login = admin
    db.jdbc.url
    Change the JDBC connection string to the target database in the following format:
    jdbc:oracle:thin:@<host>:<port>:<sid>
    <host>— name/IP of the database machine
    <port>—database listener port number
    <sid>—database SID
    Example:
    javax.jdo.option.ConnectionURL: jdbc:oracle:thin:@acmedb.acme.com:1521:orcl
    ales32_admin\config\
    asiadmin.xml
    DatabaseAuthenticator properties:

    config__database_user_login
    config__database_user_password
    If necessary, change the name and password of the OES database user in the target database within the <object id="DatabaseAuthenticator"> definition.
    To encrypt the password, use ales32-admin\bin\encrypt_password.bat|sh.
    Note: Not necessary if the target database uses the same username and password for the OES database user (default = admin, password).
    Example:
    <property name="config__database_user_login">
      <value>&quot;admin&quot;</value>
    </property>
    <property name="config__database_user_password">
      <value>&quot;{salt}g7fVAbmt8rHELa1XZ5X0xbHUMCSlN2f/&quot;</value>
    </property>
    DatabaseAuthenticator property:
    config__j_d_b_c_connection_u_r_l
    Change the JDBC connection string to the target database. Example:
    <property name="config__j_d_b_c_connection_u_r_l">
      <value>&quot;jdbc:oracle:thin:@acmedb.acme.com:1521:orcl&quot;</value>
    </property>
    ales32_admin\asiDomain\
    config\config.xml
    <sec:authentication-provider
    xmlns:ext="http://www.bea.com/ns/weblogic/
    90/security/extension"
    xsi:type="ext:database-authenticatorType">
    If the Administrator Server container is WebLogic Server 9.0 or later, modify the jdbc connection string, database user name, and password.
    To achieve password encryption, enter the password in clear text and restart WebLogic server. The restart should encrypt the password.
    Note: Not necessary to change the username and password if the target database uses the same values (default = admin, password).
    Examples of the pertinent definitions are shown below:
    <ext:jdbc-connection-url>jdbc:oracle:thin:@acmedb.acme.com:1521:orcl</ext:jdbc-connection-url>
    <ext:database-user-login>admin</ext:database-user-login>
    <ext:database-user-password-encrypted>{3DES}u6iQ9mLdY1xy6mLiSJrXyg==
    </ext:database-user-password-encrypted>

  3. If necessary, use the asipassword command to add the OES database user on the target database to password.xml.

    4. This is not necessary if the target database uses the same username and password for the OES database user (default = admin, password).

    For information about asipassword, see the Administration Reference guide.

  4. If the administration server is running on Tomcat or Websphere, run the propagateInitialCache.bat batch processing file found under the ales32-admin\bin directory.
  5. Start the SCM and Administration Server.
  6. Log into the Administration Console and modify the asiadmin SSM configuration’s Database Authenticator to point to the target database.

  Back to Top       Previous  Next