The System Management Hub is Software AG's cross-product and cross-platform product management framework. Its platform-independent, XML-based architecture provides generic rendering engines for HTML, batch etc. and standard interfaces for application development (HTML, WML, native C/C++, native Java, etc.)
The System Management Hub's architecture permits plug-in integration of existing products, separation of implementation-specific management technologies and re-use as a product-independent, cross-platform framework.
This document provides a general overview of the following topics and links to the respective detailed documentation:
UNIX users, see also Startup Daemon 'etbsrv' under Post-installation Steps under UNIX.
The EntireX-specific System Management Hub agents are installed automatically when the EntireX Administration component is installed. During installation, an initial administrator must be specified. The user ID and password of that administrator must be used at first login to the System Management Hub. That System Management Hub administrator can define additional administrators as required.
Important:
When logging in under Windows on a domain-based PC,
where the SMH administrator's initial login included the domain name, always
specify this domain name (i.e.
myDomain\myUserId).
Logging in with user ID only will return an error.
To produce and find the Broker stublog for SMH
Set ETB_STUBLOG in the system environment variables to
"1", "2" or
"3".
Reboot.
The log (trace) file will be called *.etb and will be in Documents and Setting\SAGUSER\My Documents\Software AG\EntireX.
For more information on the Broker stublog, see Tracing for Broker Stubs under z/OS | UNIX | Windows | z/VSE.
System Management Hub functionality is provided for managing the following EntireX components:
System Management Hub agents are installed on every host where an EntireX is installed. These hosts are called Managed Hosts in the System Management framework. Managed hosts form the top level list in the System Management Hub tree view. With the agents the local resources of the managed hosts are managed. For EntireX these resources are brokers, broker agents, RPC servers, and directories for authorization rules. There are two exceptions where these resources are not local resources.
Brokers may be remote Brokers which do not reside on the managed host but elsewhere on the network.
Directories for authorization rules may be somewhere on the network. This is true in particular for LDAP servers. For flat file directories, we recommend using the local file system of the managed host.
EntireX Broker instances are administered from the EntireX Broker System Management Hub node. The EntireX Broker node is located below the EntireX node in the System Management Hub tree view. Local broker instances are automatically defined to the System Management Hub and do not have to be defined by the user. When the EntireX Broker node is expanded, all of the user-defined remote Broker instances and all local Broker instances that are managed with the System Management Hub are listed. The list consists of all the Broker instances configured on the node running the System Management Hub ("local" brokers) and Broker instances configured on other nodes that the user has defined to the System Management Hub ("remote" brokers).
For more information, see Broker Administration using System Management Hub under UNIX | Windows.
The System Management Hub RPC server agent provides a user-friendly interface for managing and monitoring the EntireX RPC servers.
For more information, see Administering the EntireX RPC Servers using System Management Hub under UNIX | Windows.
An authorization rule is used to perform an access check for a particular
Broker instance against an (authenticated) user ID and list of rules. Checks are
performed on a UNIX or Windows Broker kernel, using standard EntireX Security on
these platforms. Authorization rules can be stored within a repository. When an
authorization call occurs, the security exit performs checks based on the values
of Broker attributes
AUTHORIZATIONDEFAULT and
AUTHORIZATIONRULE.
See Administering Authorization Rules using System Management Hub under UNIX | Windows.
EntireX Java Message Services are managed from the EntireX Java Message Service System Management Hub node. The EntireX Java Message Service node is located below the EntireX node in the System Management Hub tree view. Instances of Queue Connection Factories, Queues, Topic Connection Factories and Topics can be created, modified and deleted from the System Management Hub.
For more information see EntireX Message Service Administration using System Management Hub.
See the separate System Management Hub documentation.
