Frequently asked questions about Application Servers

This topic provides the frequently asked questions related to Application Servers.

• Which ports need to be opened for communicating with a client, residing behind the firewall, and using NSH?

  By default, primary communication port from Application Server to each managed host is 4750. 
  Apart from the above mention port, the following ports are important in BBSA environment. These ports should be opened based upon the configuration on need basis: 

  • 9840 - Authentication Serivce
  • 9841 - Application Server
  • 9842 - NSH Proxy Server
• I have multiple Application Servers but I cannot see all Application Server status in the Infrastructure Manager window.

  In this case, you need to synchronize the bladelogic.keystore across all Application Servers.

  See To synchronize keystore files of multiple Application Servers for more information.

• Where can I find sizing recommendations for Application Servers?

  You can find recommendations for sizing Application Servers in Sizing-Application-Servers.

• What do I do if my Application Server will not start up?

  The following list shows some common causes for this issue:

  • Review the Application Server log and look for a Java stack trace; this usually indicates the issue.
  • A few common things can cause problems with the Application Server start up:
    • The File Server RSCD Agent is not licensed (for pre-8.2 versions).
    • ACLs were pushed to the File Server agent.
      • Add a 'System:System  rw,map=<root|Administrator>' to the users.local on the File Server agent.
• Where is the TrueSight Server Automation Application Server log that contains deployment messages?

  <INSTALLDIR>\br\<deployment name>.log
   
   The default deployment name is appserver, while other common deployments have names such as job-1.