Administering the Application Server Domain for Service Registry

The configuration process for Service Registry by default creates an Application Server domain named registry, to which the Service Registry web application is deployed. This domain is in the RegistryDomain-base/domains/registry directory.

This location is different from the default location for Application Server domains, /var/opt/SUNWappserver/domains (Solaris) or /var/opt/sun/appserver/domains (Linux).

To administer the registry domain, you can use the Application Server Administration Console (“Admin Console”). You can use the Admin Console to start and stop the domain, view the server log, and perform other administrative tasks. See To Use the Application Server Admin Console for details.

You can also examine the server log directly. The log is in the file RegistryDomain-base/domains/registry/logs/server.log.

You can also use the asadmin command to administer the registry domain. Because the domain is not in the default location, you must specify the --domaindir option when you use asadmin commands that provide that option.

The password file for the registry domain is ServiceRegistry-base/pw.txt. Specify this password file as the argument to the --passwordfile option of asadmin commands when you administer the registry domain.

The registry domain uses a set of non-default ports so as not to cause conflicts with the default Application Server domain, domain1. Table 1–2 lists and describes these ports. For more information, see Ports in the Application Server in Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide.

To Use the Application Server Admin Console

Steps

1. In a web browser, go to the URL https://hostname:6489/.

   hostname is the system on which Application Server and Service Registry are running.

2. Accept the certificate that is offered.

   A login page appears

3. On the login page, type admin in the User Name field.

4. Type the Application Server administrator password in the Password field. Use the value that you specified for the AdministratorPassword property when you configured the Registry. The default is 12345678.

5. Click Log In.

See Also

For details on using the Admin Console, refer to the online help for the Admin Console or to the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide.

To change the logging level for Service Registry, follow the instructions in To configure log levels in Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide. The property to specify in the Additional Properties area is org.apache.commons.logging.simplelog.log.org.freebxml.omar.

To Stop and Restart the Application Server Domain for the Registry

The configuration process for the Registry starts the Application Server domain in which the registry is deployed. After you perform certain administrative tasks, you need to stop and restart the domain. Examples of such tasks are Allowing Access to External Web Sites and Creating an Administrator.

The Admin Console informs you if you need to restart the domain. You can use the Admin Console to perform this task. If you are using the asadmin command, you can use Ant tasks to stop and start the domain.

Steps

1. Change to the Service Registry install directory.

   cd ServiceRegistry-base/install

2. Run the following command (all on one line):

   Solaris: /usr/sfw/bin/ant -f build-install.xml appserver.domain.bounce

   Linux: /opt/sun/bin/ant --noconfig -f build-install.xml appserver.domain.bounce

   This target stops the domain and then restarts it.

   The build-install.xml file also contains separate Ant targets for stopping and starting the Registry domain. To stop the domain, use the Ant target appserver.domain.stop. To start the domain, use the Ant target appserver.domain.start.