Your Federal Quarterly Tax Payments are due April 15th Get Help Now >>

Introduction to System Management Hub for webMethods EntireX Introduction to by thejokerishere

VIEWS: 0 PAGES: 4

									Introduction to System Management Hub for webMethods EntireX   Introduction to System Management Hub for webMethods EntireX




Introduction to System Management Hub for
webMethods EntireX
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 (DCOM, 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 chapter provides a general overview of the following topics and links to the respective detailed
documentation:

      Initial Login Considerations

      Broker Stub Log

      Functional Scope of System Management Hub

      More Information

For installations under UNIX (Solaris) see also Setting Kernel Parameters.



Initial Login Considerations
The EntireX-specific System Management Hub agents are installed automatically when the EntireX
software is installed. The person who installs the EntireX software becomes, by default, the System
Management Hub administrator. 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.

When logging in, always specify the domain name. Logging in with user ID only will return an error.
Only when the domain is specified does the logon function properly.


Broker Stub Log
    To produce and find the Broker stub log for SMH

  1. Set ETB_STUBLOG in the system environment variables to "1", "2" or "3".

  2. Reboot.

  3. The log (trace) file will be called *.etb and will be in Documents and Setting\SAGUSER\My
     Documents\Software AG\EntireX.




                                                                                                                         1
Introduction to System Management Hub for webMethods EntireX      Functional Scope of System Management Hub




For more information on the Broker stub log, see Tracing for Broker Stubs under UNIX | Windows.


Functional Scope of System Management Hub
System Management Hub functionality is provided for managing the following EntireX components:

     Managed Hosts and EntireX System Management Hub Agents

     Managing the Broker

     Managing the RPC Servers

     Managing the Broker Agent

     Managing DCOM Hosts

     Managing Location Transparency

     Managing Authorization Rules

     Managing the Java Message Service

Managed Hosts and EntireX System Management Hub Agents
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, DCOM hosts, and
directories for location transparency and 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 location transparency and 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.

Managing the Broker
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.




2
Managing the RPC Servers                   Introduction to System Management Hub for webMethods EntireX




Managing the RPC Servers
The System Management Hub RPC server agent provides a user-friendly interface for managing and
monitoring the EntireX RPC servers.

For more information, see Setup and Administration of the EntireX RPC Servers using System
Management Hub under UNIX | Windows.

Managing the Broker Agent
A broker agent is a "dummy broker" that acts as a transport protocol converter or relay node for broker
calls.

For more information, see Broker Agent Control using System Management Hub under UNIX | Windows.

Managing DCOM Hosts
EntireX DCOM brings the DCOM programming model to non-Microsoft platforms in a manner that is
true to the original programming model and wire protocol. DCOM offers sufficient technical and semantic
advantages over existing communications solutions to justify the effort of bringing it to platforms such as
mainframes and UNIX.

The System Management Hub enables administrators to perform management tasks for DCOM Hosts.

For more information, see Managing DCOM Hosts with the System Management Hub.

Managing Location Transparency
Location transparency introduces the concept of logical services translated into real services. EntireX
Broker applications supporting this concept can change the real Broker ID and class/server/service entries
without having to configure anything or to change client and/or server programs.

You can add and modify logical services entries using the System Management Hub.

For more information see Location Transparency Administration using System Management Hub under
UNIX | Windows.

For general information see Location Transparency with EntireX.

Managing Authorization Rules
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 Authorization Rule Administration using System Management Hub under UNIX | Windows.




                                                                                                             3
Introduction to System Management Hub for webMethods EntireX                        More Information




Managing the Java Message Service
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 Java Message Service Administration using System Management Hub.


More Information
The full System Management Hub Documentation is also provided. This was the most recent SMH
documentation when this version of EntireX was released. As System Management Hub release cycles are
independent of EntireX, a more recent version of the System Management Hub documentation may be
available.




4

								
To top