Frequently asked questions (FAQ)

Depending on the number of topics included in the export, it might take several minutes to create the PDF. Once the export is complete, you can download the PDF.

For supported version information, see the following BMC Support Support page:
http://webapps.bmc.com/support/faces/az/prodallversions.jsp?seqid=164625
Note that as of June 26, 2012, version 7.x releases are no longer supported.

You can find information about the supported platform for BMC Server Automation on BMC Support Central, under Product Availability and Compatibility.

The BMC Knowledge Base (which includes answers for common problems with BMC Server Automation) is located at https://kb.bmc.com/infocenter/index?page=answers.

See the ports and protocols list.

You can find the build number for the various 8.3 releases (base version, SPs, and patches) in the "Current build information" section of the Preparing for upgrade topic.

See the following documentation resources:

• For information about enabling the retrieval of change information from BMC BladeLogic Server Automation for Probable Cause Analysis (PCA), see the chapter about integrating with BMC Server Automation in the BMC ProactiveNet User Guide.
• For information about transferring data to BMC PATROL and BMC ProactiveNet regarding the status, availability, and performance of hosts and servers managed by BMC Server Automation, see the online documentation for BMC PATROL for BMC Server Automation and BMC ProactiveNet Automation Server Monitoring.

You can find information about the supported upgrade paths for BMC Server Automation in the Upgrading section of the online technical documentation (in the Preparing for upgrade topic).

You can find deployment architecture recommendations in the following Planning section: Deployment architecture

See Upgrading custom configuration objects.

Use the following process:

1. Start by looking at the rscd.log. Who are your requests currently mapping to? If it is someone who does not exist in your users or users.local file, consider adding a temporary definition for them.
2. Remove the "nouser" line from the users file.
3. Change the contents of the exports file so that it contains a single line: "* rw,user=root" or "* rw,user=Administrator" (or the name of your local admin account).

Once you have finished troubleshooting, make sure to restore the original configuration.

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.

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

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

See the following Knowledge Article for information on this issue:
https://kb.bmc.com/infocenter/index?page=content&id=KA373609

You can find recommendations for sizing Application Servers in the following topics:

• Sizing Application Servers
• Application Server sizing reference

You can find a list of user contributed tutorial information in the BMC Contributor topics topic.

In addition, the taking the reins article on Communities includes additional videos and "how to" information.

You can find helpful videos in the following topics:

• Installing BMC Server Automation on Windows
• Installing the BMC Server Automation Console and Network Shell (Windows)
• Setting up a SQL Server database, user, and schema for BMC Server Automation
• Configuring two RSCD agents on a single host
• Analyzing system compliance
• Loading Compliance Content

In addition, the taking the reins article on Communities includes additional videos and "how to" information.

On UNIX, look in /etc/lib/rsc/HOME or /usr/lib/rsc/HOME. If that file does not exist, you are running a local or self-contained installation, and will need to derive the installation location from running processes. For example:

Linux:

ls -la /proc/`ps -ef | grep rscw | grep -v grep | awk '{print $2}'` | grep exe | awk '{print $11}'

Solaris:

pargs -l `ps -ef | grep rscd | head -1 | awk '{print $2}'`

On Windows: INSTALL_DIR\RSCD\rscd.log

On UNIX: INSTALL_DIR/[NSH|RSCD]/log/rscd.log

<INSTALLDIR>\Transactions\log\bldeploy-xxxx.log

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

For detailed instructions on analyzing the Trace.txt file, see How to analyze Trace.txt generated by a Windows Patch Analysis Job (user contribution).