Ask a question?
  • Contact Us
  • Support Case System
  • Support Forum

I can't start my Admin Assistant. What do I do?

The Multi-Tier Administrative Assistant is a service. It is powered by the www_sv agent that appears in the /bin/w3config sub-directory of Multi-Tier server components installations. Unlike the Request Broker, the Administrative Assistant does not require manual startup. Instead, the Request Broker spawns the agent during its own startup routine. Here is the portion of the Rules Book (oplrqb.ini) that automates this task:

[Persistent Services]
Configurator = www_sv

[www_sv]
Program     = w3config/www_sv
Directory   = w3config
CommandLine =

If the Admin Assistant fails to start, take the following action:

  1. Insure that the Request Broker process (oplrqb) is running.
  2. Insure that the [Persistent Services] and [www_sv] sections appear in the Session Rules Book. The Session Rules Book is the oplrqb.ini file that appears in the /bin sub-directory of the Multi-Tier server components installation.
  3. Insure that www_sv appears in the /bin/w3config sub-directory of the Multi-Tier server components installation.
  4. Execute www_sv -?. Stop and report errors, if they occur.
  5. Use a text editor to open the www_sv.ini file that appears in the /bin/w3config section of the Multi-Tier server components installation. Look for the HttpPort parameter. Record the value and exit the file.
  6. Run netstat -a to see if another service is using the port passed by HttpPort. Assign a new HttpPort, if this is the case.
  7. Use a text editor to open the oplrqb.log file that appears in the /bin sub-directory of the Multi-Tier server components installation. Stop and report errors, if they occur.
  8. Use a text editor to open the www_sv.log file that appears in the /bin/w3config sub-directory of the Multi-Tier server components installation. Stop and report errors, if they occur.

www_sv -? may report library errors on Unix systems. Users can remedy library errors by taking the following actions:

  1. Use find / -name -print to find the missing library.
  2. Pass the path to the library to LD_LIBRARY_PATH, LIBPATH (AIX), or SHLIB_PATH (HP/UX).
  3. Restart the Request Broker service.
  4. Test