Make Sybase Control Center aware of an ESP node (acting as a cluster
manager, controller, or both) and its connection information by registering it as a
resource.
- In the Resource Explorer, select
- Specify:
New Resource Type Details
Field |
Description
|
Resource Name
|
(Required)
Name of the resource to register. Set a name which will make
the ESP node easily identifiable. |
Resource Type
|
Select ESP Node. |
Description |
(Optional)
A brief description to help you identify the resource. |
- Click Next.
- Specify the connection information for your resource:
New Resource Connection DetailsField |
Description |
Host Name |
(Required) Name of host on which the ESP node runs.
Default value is localhost. |
Port Number |
(Required) Port number for the ESP node. |
SSL is Enabled (Y/N) |
(Required) Specify Y if SSL is enabled on the ESP Server,
and N if it is not. |
- Click Next.
- Enter authentication information based on the authentication type
you specified while installing Event Stream Processor. This information is stored in the
ProductModule.xml file, and must match the authentication type
of the cluster in Event Stream Processor.
Authentication Type |
Fields |
Native OS |
User name and password. |
LDAP |
User name and password. |
Kerberos |
KDC, Realm, Service Name, User name, and Ticket Cache Location. See the
Event Stream Processor Administrators Guide for more
information. |
RSA |
User name, Password, and Keystore location. |
- Or if you prefer not to authenticate now, click I do not want
to supply authentication information.
- Click Next.
- (Optional) Click Add this resource to the current perspective. You must add a resource to a perspective (not necessarily the current perspective) before you can manage or monitor it.
- (Optional) Click Open the resource explorer to view this new resource. (This option is not present when the Resource Explorer is open.)
The resource is added to the Resource Explorer even if you choose not to view it.
- Click Finish.
The ESP node is registered. If you have chosen to authenticate the
resource and the authentication is successful, the other active nodes that
belong to the same cluster as this node are registered and authenticated
automatically because in Event Stream Processor, authentication is performed on
a cluster-wide basis rather than on a per-node basis. These other nodes are
named "<cluster_id>_<node_id>", by default, and
"<cluster_id>_<node_id>(manager)" is for both manager type and dual
(manager and controller) type nodes. You can edit the names of these nodes under
resource properties.