Configure Sentinel objects and monitoring

This section describes the required post-installation steps to set up the prepackaged Visibility objects, and activate SSL for event acquisition.

  • Tracked objects and Requests
  • Alerts
  • Commands
  • Reports
  • Monitoring
  • Secure Event Acquisition listener
Note Stop Sentinel before performing the operations described in this section.

Tracked objects and Requests

Central Governance delivers predefined Tracked Objects and Requests that you must install on Sentinel for Visibility services.

Copy the TrackingObject and Request folders as follows.

From:

  • <CG_installation_directory>/resources/sentinel-distrib-cg.zip/content/predata/common/broadcast/commit/TrackingObject
  • <CG_installation_directory>/resources/sentinel-distrib-cg.zip/content/predata/<Sentinel database type>/broadcast/commit/Request

To:

  • <Sentinel_installation_directory>/Sentinel/broadcast/commit/TrackingObject
  • <Sentinel_installation_directory>/Sentinel/broadcast/commit/Request

Alerts

Configure the predefined Central Governance Alerts in Sentinel.

  1. Copy the Rule folder content from <CG_installation_directory>/resources/sentinel-distrib-cg.zip/content/predata/common/broadcast/commit/Rule to <Sentinel installation directory>/Sentinel/broadcast/commit/Rule.
  2. To correct an issue with the delivered correlation rules, make the following changes depending on:
    • If the default rules were not previously updated on Sentinel, on Sentinel overwrite the Rule folder with <CG_installation_directory>/resources/sentinel-distrib-cg.zip/content/predata/broadcast/commit/Rule
    • If the default rules were previously modified on Sentinel, you must edit the xml for each of these correlation rules and replace the TrkCreateRuleVar and TrkSetRuleVar functions with the TrkCreateEventVar and TrkSetEventVar functions. The signatures of the functions are the same so you need only change the names.
    • In either case, you must restart Sentinel for the update to be taken into account.
  3. Copy the exit content from <CG_installation_directory>/resources/sentinel-distrib-cg.zip/content/sentinel/exit/sentinel-exit-function.jar to <Sentinel installation directory>/Sentinel/exit.
  4. Edit the <Sentinel installation directory>/Sentinel/conf/trkserver.xml file.
    • Go to the section <Server id="RuleServer" type="Rule">.
    • Add the ExitCmd tasks to the RuleServerConfig section.

    <Server id="RuleServer" type="Rule">

        <Common>

          <Custom activated="true" mandatory="false" serverRmiHostName="localhost"/> 

          <Fixed class="RuleServer" package="com.axway.sentinel.rule.server"/>

        </Common> 

        <Specific>

    <RuleServerConfig>

    <Processing threadsPoolSize="20" timerCorePoolSize="5" timerKeepAlive="60000" timerMaxPoolSize="10" timerQueueCapacity="500000"/>

    <ExitCmd class="EncodeUrlFunction" package="com.axway.nodes.sentinel.exit.function" type="cmd_extend"/>

    <ExitCmd class="ReplaceSpacesFunction" package="com.axway.nodes.sentinel.exit.function" type="cmd_extend"/>

    <ExitCmd class="GetFlowsReportUrlFunction" package="com.axway.nodes.sentinel.exit.function" type="cmd_extend"/>

    <ExitCmd class="GetCGUrlFunction" package="com.axway.nodes.sentinel.exit.function" type="cmd_extend"/>

    </RuleServerConfig>

        </Specific>

    </Server>

  5. Add the following properties to the <Sentinel installation directory>/Sentinel/conf/server.properties file:
  6. axway.cg.frontend.port=<CG UI port (default 6900)>

    axway.cg.frontend.url=https\://<CG_FQDN>\:<CG UI port>

Note The TrkGetFlowsReportUrl function builds the URL needed to connect to Sentinel when accessing the Flows Report page. It parses the server.properties file to look for the axway.cg.frontend.url property, which points to Central Governance.

Commands

Central Governance delivers pre-defined commands that are executed from the Sentinel Web Monitoring and Web Dashboards interfaces.

Execute the following steps to setup commands:

  1. Copy the Command folder content from <CG_installation_directory>/resources/sentinel-distrib-cg.zip/content/predata/common/broadcast/commit/Command folder to <Sentinel installation directory>/Sentinel/broadcast/commit.
  2. Copy the <CG_installation_directory>/resources/sentinel-distrib-cg.zip/content/sentinel/exit-command folder content to <Sentinel installation directory>/Sentinel.
  3. The commands use mutual SSL to connect to the Central Governance Core Services. Add the following properties to the <Sentinel installation directory>/Sentinel/conf/server.properties file:

conf.um.opnode.wapi.host=<CG_FQDN>

conf.um.opnode.wapi.port=<CG Core Service Port (default 8081)>

conf.um.opnode.wapi.keystore=<Sentinel installation directory>/Sentinel/conf/security/PAMKeystore.jks

conf.um.opnode.wapi.keystorePwd=u9jkVm/WHFn+OZyQILRJNQ==

conf.um.opnode.wapi.truststore=<Sentinel installation directory>/Sentinel/conf/security/truststorePassPort.jks

axway.sentinel.xfbtransfer.laststate.name=ENDED

Web Dashboard Reports

  1. In the <Sentinel install directory>/Sentinel/conf/server.properties file, add:
    webdashboard.schema.independent.import=true

    Perform this operation with Sentinel stopped as this setting requires a Sentinel restart to be taken into account.

  2. Copy the <CG_installation_directory>/resources/sentinel-distrib-cg.zip/content/sentinel/jetty/webapps/SentinelWebdashboard/preimport/<Sentinel database type> folder content.
  3. Archive the data.xml and export.xml files in ZIP format. The archive should be comprised of only the .xml files and not the folder in which they are located.
  4. Copy the zip archive to the <Sentinel install directory>/Sentinel/jetty/webapps/SentinelWebDashboard/import folder. The import occurs when you next start Sentinel.
  5. In some instances, for example when using Axway Desktop Client, your configuration may require access by a hostname or IP address other than the one specified in the Central Governance conf.um.opnode.wapi.host parameter. To enable this access, add the additional hostnames as a comma-separated list for the referer.hosts.accepted parameter in the <Sentinel install directory>/Sentinel/conf/server.properties file.
  6. referer.hosts.accepted=<Other_CG_hostname1>,<Other_CG_hostname2>

Monitoring Web

Copy the config folder content from <CG_installation_directory>/resources/sentinel-distrib-cg.zip/content/sentinel/jetty/webapps/SentinelMonitoring/WEB-INF/config to <Sentinel installation directory>/Sentinel/jetty/webapps/SentinelMonitoring/WEB-INF/config.

Secure Event Acquisition listener

Central Governance sends event notifications about the SSL connection. Additionally, you can configure managed products to send event notifications to Sentinel via the SSL connection. To do so you need to activate the acquisition front-end server port for SSL.

Edit the <Sentinel installation directory>/Sentinel/conf/trkserver.xml:

  1. Navigate to the <Server id="FrontEndServer" type="FrontEnd"> section, <FrontEndServerConfig> subsection.
  2. Locate the service with id="QLT-XML" in the SrvImpl element. The default port is 1303.
  3. Change the class attribute value from SocketEventReceiver to SecuredSocketEventReceiver.

Example

<Service activate="true" host="SentinelHost" id="QLT-XML" poolSize="10" port="1303">

<Description>QLT server tracker for XML data type</Description>

<SrvImpl class="SecuredSocketEventReceiver" package="com.axway.sentinel.frontend.server.services.socketevent" protocol="QLT"/>

</Service>

 

Central Governance | Document Directory

Related Links