Support Downloads About Us

Using enterprise-Q, Endpoints can be automatically managed via user-defined Endpoint Login rules. When an Endpoint logs into its Gateway, target data elements collected in Endpoint Login Policy are passed to the enterprise-Q server. In turn, the EPLogin transaction is executed which processes the established Endpoint Login rules. As the rules are processed, the appropriate transactions are queued and executed (via enterprise-Q) to automatically manage all Endpoints in the Tivoli Managed Environment (TME).

Endpoint Login rules-based processing includes:
  1. Excluding Endpoints from Login Policy processing
  2. Upgrading Endpoints to newer version of the agent
  3. Migrating Endpoints to another Tivoli Gateway
  4. Assigning Endpoints to a Policy Region
  5. Subscribing Endpoints to Profile Managers (a.k.a. Subscription Lists)
The following data elements may be used in Endpoint Login rules processing:
  • Endpoint Label
  • Endpoint Version
  • Endpoint Interp
  • Tivoli Gateway
  • IP Address
After installing enterprise-Q, you may begin creating EPLogin rules by clicking on the Endpoint Mangement link on the front page to get to the following page:

From this page, click on the Login Policy Configuration link to show this page:

Now, click on the each rule button and define rules that match your criteria. Once all the EP Login rules are defined, they can be tested by clicking the Test Rules button and entering Target test data elements. Click here to learn more about testing EP Login rules.

EPLogin Exclude Rule
This rule is used to exclude Targets from Endpoint Login processing.

In the example below, we are excluding those Targets that have an IP address within our dial-up modem range, as well as those computers that begin with the letters 'SRV'.

EPLogin Upgrade Rule
This rule is used to determine which Endpoints need to be automatically upgraded to a newer version of the agent. When so determined, the EPUpgrade transaction is queued to execute if the Endpoint must be upgraded based on the rules specified.

In the example below, we suppress Endpoint upgrading if the Endpoint is coming from Gateway 'expresso_gw' or if the IP address of the Endpoint falls within our dial-up modem range. Furthermore, we only upgrade if the current version of the agent is less than 93.

EPLogin Migrate Rule
This rule is used to migrate Endpoints to their proper Gateway. When so determined, the EPMigrate transaction is queued to execute if the Endpoint must be migrated based on the rules specified.

In the example below, we use the IP address of the Endpoint to determine which Gateway the Endpoint belongs. If the Endpoint is logged in via dial-up modem, we skip the migration. By default, we migrate the Endpoint to its preferred Gateway.

EPLogin Link Rule
This rule is used to determine the Endpoint's Policy Region assignment. When so determined, the LinkTarget transaction is queued to execute if the Endpoint must be moved to a new Policy Region based on the rules specified.

In the example below, we use the Endpoint's Gateway to specify the Policy Region to which the Endpoint belongs.

EPLogin Subscribe Rule
This rule is used to determine all the Profile Managers to which the Endpoint should be subscribed. All if-statements are processed to determine the entire set of Profile Managers. If none are determined, and a default is specified, the default Profile Managers are considered. When so determined, the Subscribe transaction is queued to subscribe the Endpoint to each Profile Manager to which is is not already subscribed. Furthermore, if the UnSubscribe flag is set, an UnSubscribe transaction is queued to unsubscribe the Endpoint from each Profile Manager to which it is subscribed, but not determined based on the rules specified.

In the example below, all Endpoints are subscribed to a single Profile Manager. Of course, your rule will undoubtedly be more involved.

Testing EP Login Rules

To test the EP Login rules, click the Test Rules button from the EP Login Configuration page. The following new browser windo will appear:

From here, enter some test data and click the Test button. The EPLogin transaction executes in test mode, processing each rule using the data supplied. The results of processing each rule are displayed in the green bars. If-statement processing details are displayed below each green bar.

Here is some sample Test Rules output:

In some cases, if-statement processing may result in a number or null-string. These values are processed internally to determine the actual result as it pertains to the rule being processed.

Go to Rapid Deployment Tools -->