Central Server Routers and the Infrastructure Management REST API

This section explains how a Central Server Router handles Infrastructure Management REST API requests.

This feature is deprecated in 11.3.04. Some of the links in this page could point you to an older version of the documentation.

Central Server Router

A Central Server Router is a BMC TrueSight Infrastructure Management Server that is set to function as a router. A router is used in a setup that has multiple Child Servers. It routes REST API requests to the corresponding Child Servers. It also collects the responses from these servers and sends them to the REST API client.

Architecture of Central Server Router for REST API

Infrastructure Management architecture for multiple BMC TrueSight Infrastructure Management Servers explains the architecture of a Central Server Router with multiple Child Servers.

The router receives REST API requests from a REST API client. It authenticates user credentials against the information in the Infrastructure Management Database or the LDAP server and directs the requests to the corresponding Child Servers. The child servers send their responses to the router, which cumulates the responses and sends them to the REST API client.

For information about the authentication process, see Authentication-for-the-Infrastructure-Management-REST-API.

Setting a BMC TrueSight Infrastructure Management Server as a Central Server Router or a Child Server

When you install BMC TrueSight Infrastructure Management Server, you have the option of setting the server either as a Central Server Router or a Child Server. For information, seeConfiguring the Infrastructure Management Server as a Central Server Router or a Child Server manually

You can also change the setting after the installation by executing the pw configwsroles CLI command.

Log files for REST API related to Central Server Router

The errors and exception messages of the APIs that are related to Central Server Router are logged on to the following log files:

  • sapws.log
  • bppmws.log
  • ProactiveNet.log

The log files are located in the \pw\pronto\logs folder.

The following debug log files also record the errors and exception messages if you have enabled them:

  • sapws.debug.log
  • bppmws.debug.log
  • jserver.log

The debug log files are located in the \pw\pronto\logs\debug folder.

For information about the log files, see Logs-for-the-Infrastructure-Management-REST-API.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*