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 OS) or /var/opt/sun/appserver/domains (Linux and HP-UX systems).

It is recommended that you not run any applications other than Service Registry in the registry domain.

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.

In addition to the Admin Console, you can 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 argument to the --domaindir option is RegistryDomain-base/domains.

If you want to use the --passwordfile option of asadmin commands, you need a file with a copy of the administrator password for the Registry domain. To create such a file, use the generate.password.file target of the build-install.xml file. The file is RegistryDomain-base/3.0/data/security/pw.txt.

The registry domain uses a set of non-default ports so as not to cause conflicts with the default Application Server domain, domain1. These Service Registry port values are registered with the Internet Assigned Numbers Authority (IANA). 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.2 Administration Guide.

To Use the Application Server Admin Console

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.

   If you changed the default value of the registry.install.AdministratorUserID property when you configured the Registry, type the value you specified.

4. Type the Application Server administrator password in the Password field. Use the value that you specified for the registry.install.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.2 Administration Guide.

Changing the Service Registry Logging Level

To change the logging level for Service Registry, follow the instructions in the Admin Console online help. The property to specify in the Additional Properties area is org.freebxml.omar.

To change the logging for particular Service Registry subcomponents, refer to the following file: RegistryDomain-base/domains/registry/applications/j2ee-modules/soar/WEB-INF/classes/log4j.properties. You can specify any of the subcomponent names listed in this file. Do not include the string log4j.logger. For example, you can log server calls by specifying org.freebxml.omar.server.

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 Configuring the Java Virtual Machine (JVM) for the Registry Domain 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.

1. Change to the Service Registry install directory.

   cd ServiceRegistry-base/install

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

   Ant-base/ant -f build-install.xml -Dinstall.properties=props-file appserver.domain.bounce

   where props-file is the path name of the copy of install.properties file that you edited in To Configure Service Registry as Root Using Custom Properties After a Configure Later Installation or To Configure Service Registry as a Non-Root User Using Custom Properties After a Configure Later Installation.

   The appserver.domain.bounce 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.