Start component
This option is only available if a component is selected in the Navigation Pane. It is equivalent to pressing the
button on the toolbar.
Choose this option to start the currently selected component. The component’s icon will change to indicate that the component is starting, and then to show it is operational. Note that this can take a few seconds since the icon is only updated once EMM can satisfactorily communicate with the component.
A component can fail to start for several reasons. The most common are:
A valid license was not available on that host.
The Sentinel Agent is not running on the host (check that its icon in the Navigator Pane is
and not
)
The component’s executable was corrupt, or inaccessible due to user permissions issues.
The component’s listening port was not available as it is in use by something else.
There was insufficient disk space on that host for the Sentinel Agent’s or the component’s logging.
The component could not write to the specified log file due to user or file permissions issues.
The component could not locate its essential runtime libraries. Either the component or the libraries it requires were manually moved, or the environment variables are set incorrectly on that host.
You might have set important management and configuration parameters but forgotten to commit them.
The component might appear not to have started even though in fact it has, due to a firewall blocking the port that the EMM console uses to communicate with the component. The firewall must be disabled or reconfigured to allow traffic on the port the component is configured to listen on.
The Sentinel Agent on that host could not locate the component’s binary. This means it was not configured correctly; normally this is due to it not having had valid component paths specified.
Note: All components started by the Sentinel Agent are started under the same user context (and therefore with the same privileges) as the user the Sentinel Agent itself was started as.
Therefore, if the Sentinel Agent was started as a service as the user Local System, all the components it starts will also start as the user Local System. Note that Local System is not a Windows Domain user, and therefore might not be allowed access to Domain resources. This might be particularly relevant to IAF adapters which link against custom user code and are likely to require access to various network services and resources.
If this situation is encountered, you need to change the user that the Sentinel Agent is started as, which can be done through Control Panel, Administrative Tools, Services, right click on Apama Sentinel Agent, select Properties, then the Log On tab. Choose the This account: radio button and enter the username and password of the user to use instead. You can specify a domain user by preceding the username with the domain as follows: domain_name/username. You will of course have to be an Administrator on the machine to be able to do any of this.