Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Working with an Example

The example for setting up policy and token files shows two nodes in a cluster called `mycluster` . One node is an inference engine and the other is a cache engine.

Procedure
1. Assume that the ListenURL for the cache (controller) is `tcp://203.0.113.0:9091` and the ListenURL for the inference (requester) is `tcp://203.0.113.0:9090`.
2. Generate the policy and token files from `as_admin`.
   Edit the `metaspace_access`line in both files to set the correct cluster name. For details, see TIBCO ActiveSpaces version 2.x Documentation.
3. Also edit the line to place the ListenURL of the controller into the `discovery= setting`.

       metaspace_access=metaspace=mycluster;discovery=tcp://203.0.113.0:9091;

4. For the inference engine, you can then set the following properties:

       be.engine.cluster.as.security.enable=true
       be.engine.cluster.as.security.mode.role=Requester
       be.engine.cluster.as.security.file=C:/temp/mytoken.txt

5. For the cache engine, you can then set:

       be.engine.cluster.as.security.enable=true
       be.engine.cluster.as.security.mode.role=Controller
       be.engine.cluster.as.security.file=C:/temp/mypolicy.txt

   Note: There is no rule that caches have to be controllers, or inferences have to be requesters. The roles are interchangeable as long as there is one controller in the cluster.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.