Setting up NSH properties

To enable proxy mode to establish the extra layer of security of connections between the dispatcher server and Remote System Call Daemon (RSCD) targets, define the following properties in each level on which you want to use the NSH proxy mode (Package, Instance Channel, Environment, and so on):

  • BLCRED_PROFILE: BSA Authentication profile that points to the BMC Server Automation (BSA) application server 
  • BLUSER: User name to use for authentication
  • BLPASSWORD: Password to use for authentication
  • (Optional: 4.3.01 and laterBL_ROLE and BL_RBAC_ROLE: Nondefault role for the user
  • (Optional: 4.3.01 and later) BL_RBAC_ROLE: Nondefault role for the user
  • ( and later) BL_CRED_CACHE_FOLDER: The variable that points to the location where the cache files are stored. Dispacther has the read/write access to that folder.


To deploy targets behind an NSH proxy, you need to set the same properties as above for Channel. These properties can be set on the environment if all channels in that environment are managed by the same user/role.

Known limitations of NSH Proxy

  1. Package properties overwrite the Topology properties. Therefore, if you define the before mentioned properties in the package and these properties differ from the ones you define on the Topology tab, you must remove or overwrite the properties in order to connect to a target during the deployment.
  2. Only one User/Role can be handled per dispatcher at a time. Blcred stores a file in the same location every time it is called in NSH. If you try to do two deployments at the same time with different roles, there will be a collision and the first deployment will fail.


    Starting with BMC Release Package and Deployment, multiple users can use one dispatcher at the same time. To enable multiple users to use one dispatcher at a time, follow the steps in the Multi-user access to NSH topic.

Was this page helpful? Yes No Submitting... Thank you