Knowledgebase

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

Running Multiple Administration Servers on One Machine

Running multiple OES Administration Servers on one machine may be useful in development environments. This can be done by installing the additional servers in separate BEA_HOMES and then modifying the Window’s service names of the added server and SCM to unique values.

 

Instructions

Follow these instructions:

  1. To host the additional OES Administration Server, install an additional WebLogic or Tomcat server in a new BEA_HOME.
    2. Note: In these instructions, the new BEA_HOME is BEA_HOME2.
  2. Install the additional OES Administration Server.
    3. Note: During installation, be sure to clear the Install Database Schema checkbox.
  3. After installation, open BEA_HOME2/SCM_INSTALL/bin/WLESscm.bat in an editor and change the SCM service name in line 13 to a unique name. For example:
    4. set SERVICENAME="ALES Service Control Manager2"
  4. Open BEA_HOME2/SCM_INSTALL/config/WLESscm.conf in an editor and specify unique values as described below:

    5. line 145 — wrapper.ntservice.name=SCM2

    line 148 — wrapper.ntservice.displayname=ALES Service Control Manager2

    line 151 — wrapper.ntservice.description=ALES Service Control Manager2

  5. Change to BEA_HOME2/SCM_INSTALL/bin and run the following: 
    6. WLESscm.bat register

    If the registration is successful, the new service will appear in the Window’s Services applet.

  6. Open BEA_HOME2/ales32-admin/bin/WLESadmin.bat and change line 13 to specify the same value set in the service name from step 3 above. For example:
    7. set SCMSERVICENAME="ALES Service Control Manager2"
  7. Do one of the following:
    1. If using WebLogic server, open BEA_HOME2/ales32-admin/bin/WLESWebLogic.bat and modify line 13 as shown below:
      2. set SERVICENAME=ALES.WLS2.<host>
    2. If using Tomcat, modify line 13 in BEA_HOME2/ales32-admin/bin/WLESTomcat.bat as follows:
      3. set SERVICENAME=ALES.TOMCAT2.<host>
  8. Do one of the following:
    1. If using WebLogic server, open BEA_HOME2/ales32-admin/config/WLESWebLogic.conf and modify the following lines as shown:

      2. line 186 — wrapper.ntservice.name=ALES.WLS2.<host>

      line 189 — wrapper.ntservice.displayname=ALES WLS2.<host>

      line 192 — wrapper.ntservice.disscription=ALES WeblogicServer - WLS2.<host>

    2. If using Tomcat, modify the following lines in BEA_HOME2/ales32-admin/config/WLESTomcat.conf:

      3. line 191 — wrapper.ntservice.name=ALES.TOMCAT2.<host>

      line 194 — wrapper.ntservice.displayname=ALES TOMCAT2.<host>

      line 197 — wrapper.ntservice.description=ALES Tomcat Server2

  9. Go to BEA_HOME2/ales32-admin/bin and run the following:
    10. WLESadmin.bat register

    If the registration is successful, the new service will appear in the Window’s Services applet.

  10. Remaining in BEA_HOME2/ales32-admin/bin, run the following to install the initial policies:
    11. install_ales_schema.bat <dbuser> <dbuser_password>

  Back to Top       Previous  Next