Cloud CM-IPMP Anleitung zur Fehlerbehebung

Open Cloud Rhino SLEE 1.4.3Administration ManualVersion 1.1November 2, 2006Open Cloud Limited54-56 Cambridge TerraceWellington 6149New Zealandhttp://w

Chapter 1IntroductionWelcome to the Open Cloud Rhino SLEE Administration Manual for Systems Administrators and Software Developers. Thisguide is inten

# Build componentJarOne.jar# ...# Generate a new signing key.keytool -genkey -keystore my.keystore -alias componentSignerOne# Sign the component jar.j

Resource Adaptor SignerJ2EE Connector Resource AdaptorRhinoJ2EEConnectorRAJAIN SIP Resource AdaptorRhinoSIPRAJCC Resource AdaptorRhinoJCCRAWeb Console

The file config/ldapauth.properties contains configuration for the LDAP connection, please see the Rhino Javadoc forcom.opencloud.rhino.security.auth.LDA

Chapter 16Performance Tuning16.1 IntroductionThe Rhino SLEE will excel to production performance and stability requirements when it is configured, moni

16.2.1 ConfigurationConfigure the following parameters for staging configuration using the Web Console, or by editing and updating the stagingconfiguratio

With local staging queues enabled the new stage item will be processed immediately by the thread that created it upon termina-tion of the transaction

•stale pool size: The maximum number of objects to hold in thestalepool.•use defaults: For custom pool config MBeans only; use values from default pool

by fault tolerant Resource Adaptors). Because of the clustering infrastructure and the single management image, this allowseven applications configured

16.4.3 Fault Tolerant Resource AdaptorsWhen a fault tolerant Resource Adaptor is activated in Rhino, all activities it creates and their associated st

Chapter 17Clustering17.1 IntroductionThis chapter defines the terms and concepts used when clustering Rhino SLEE and describes several typical configura

Chapter 9 describes installation details and configuration issues of the Web Console used for Open Cloud Rhino SLEE man-agement operations.Chapter 10 d

17.2.5 Typical InstallationThe typical installation for Rhino SLEE is a 3 machine cluster, with one node running on each machine. This configuration is

17.3.1 Node FailureNode failure is defined as a node exiting the process, or the machine that the process runs on dying (possibly due to powerfailure e

Cluster [2,3]Cluster [1]Machine ARhino node 1Machine BRhino node 2Machine CRhino node 3Cluster [1,2,3]Machine ARhino node 1Machine BRhino node 2Machin

Chapter 18Application Environment18.1 IntroductionIn this chapter we;• Describe the function and configuration of MemDB the Rhino SLEE volatile memory

Synchronous Memory-to-Memory ReplicationWhen MemDB operates in this mode all replicas are consistent for every transaction.As part of the transaction

a deadlock is detected during lock acquisition.18.2.3 Multiple TransactionsMultiple MemDB instances can be used in a single transaction, as MemDB supp

The extension deployment descriptor mechanism allows a number of run-time properties of the SBB to be configured. It isimportant to note that it does n

<!ELEMENT description (#PCDATA)><!ELEMENT sbb (description?, lock-strategy?, attachment-lock-strategy?,resource-ref*)><!--The lock-stra

<!--The res-type element specifies the type of the data source. The typeis specified by the fully qualified Java language class or interfaceexpecte

the resource adaptor component jar file only. They are not granted to classesloaded from any other dependent jars required by resource adaptors define

Chapter 2The Rhino SLEE Platform2.1 IntroductionThe Open Cloud Rhino SLEE is a suite of servers, resource adaptors, tools, and examples that collectiv

SBBThis example shows fragments of the JAIN SLEE 1.0 specification defined SBB deployment descriptor, and a correspondingextension DD that informs Rhino

therefore knows that SIP transactions time out after a certain period of time. When Rhino queries the RA it will tell Rhino toend the activity corresp

Chapter 19Database Connectivity19.1 IntroductionThis chapter discusses Rhino SLEE configuration, and recommendations for programming applications which

Each <parameter> element contains a mandatory <param-name>, <param-type> and <param-value> element. Thesethree elements identi

<jdbc><jndi-name>ExternalDataSource</jndi-name><datasource-class>org.postgresql.jdbc2.optional.SimpleDataSource</datasource

For further information regarding extension deployment descriptors refer to Section 18.5 in Chapter 18.The SBB is then able to obtain a reference to a

It is recommended that these methods are not invoked by a SLEE components.Open Cloud Rhino 1.4.3 Administration Manual v1.1 117

Chapter 20J2EE SLEE Integration20.1 IntroductionThe Rhino SLEE can inter-operate with a J2EE 1.3-compliant server in two ways:1. SBBs can obtain refer

<?xml version="1.0"?><!DOCTYPE rhino-config PUBLIC"-//Open Cloud Ltd.//DTD Rhino Config 0.5//EN""http://www.openclou

<!-- other elements omitted --><ejb-ref><description> Access to remote EJB stored on a J2EE server. </description><!--The &

Service DevelopmentExample Services Service EditingFunctional TestingLoad TestingService Logic Execution EnvironmentResource AdaptorArchitectureServic

During this configuration, the Open Cloud Rhino SLEE J2EE Connector will be configured with a list of endpoints. This list isa space- or comma- separate

Chapter 21PostgreSQL Configuration21.1 IntroductionThe Rhino SLEE requires a PostgreSQL RDBMS database for persisting the main working memory to non-vo

21.4 TCP/IP ConnectionsThe PostgreSQL server needs to be configured to accept TCP/IP connections so that it can be used with the Rhino SLEE.As of versi

Figure 21.1: Cluster with mulitple database serversThe main working memory consists of several memory databases on each node.• TheManagementDatabasewh

name, user name, password, login timeout). Variable substitution using@variable-name@syntax substitutes variables fromthe$RHINO_NODE_HOME/config/confi

<datasource-class>org.postgresql.jdbc3.Jdbc3SimpleDataSource</datasource-class><dbid>rhino_sdk_management</dbid><parameter&

<param-value>@MANAGEMENT_DATABASE_NAME@</param-value></parameter><parameter><param-name>user</param-name><param

node is configured to update multiple databases.Open Cloud Rhino 1.4.3 Administration Manual v1.1 128

Chapter 22SIP Example Applications22.1 IntroductionThe Rhino SLEE includes a demonstration resource adaptor and example applications which use SIP (Se

22.2 System RequirementsThe SIP examples run on all supported Rhino SLEE platforms. Please see Appendix A for details.22.2.1 Required Software• SIP us

2.4 Service DevelopmentThe Service Development category provides a Federated Service Creation Environment (FSCE) which enables the developmentof SLEE

After changing thePROXY_HOSTNAMESandPROXY_DOMAINSproperties so that they are correct for the environment, save thesip.propertiesfile.22.4.2 Building an

sip-fmfm:[copy] Copying 4 files to /home/user/rhino/examples/sip/jars/sip/classes/sip-examples/fmfm-META-INF[profilespecjar] Building profile-spec-jar

By default, the build script will deploy the Registrar and Proxy example services, and any components these depend on,including the SIP Resource Adapt

user@host:~/rhino$ ./client/bin/rhino-consoleInteractive Rhino Management ShellRhino management console, enter ’help’ for a list of commands[Rhino@loc

The deployment descriptors for the JDBC Location SBB are located in thesrc/com/opencloud/slee/services/sip/location/jdbc/META-INFdirectory. The defaul

Name Type Default DescriptionListeningPointsjava.lang.String 0.0.0.0:5060/[udp|tcp] List of endpoints that the SIP stack will listen on. Must be speci

user@host:~/rhino/examples/sip$ ant deploysipraBuildfile: build.xmlmanagement-init:[echo] OpenCloud Rhino SLEE Management tasks definedlogin:[slee-man

# Select location service implementation.# If "usejdbclocation" property is true, JDBC location service will be deployed.# Default is to use

sip-registrar:[copy] Copying 2 files to /home/users/rhino/examples/sip/classes/sip-examples/registrar-META-INF[sbbjar] Building sbb-jar: /home/users/r

deploylocationservice:deployregistrar:[slee-management] Install deployable unit file:jars/sip-registrar-service.jar[slee-management] Activate service

The Federated Service Creation Environment allows a SLEE component or application to be fully tested under scenarios similarto the actual deployment e

sip-jdbc-location:[sbbjar] Building sbb-jar: /home/user/rhino/examples/sip/jars/jdbc-location-sbb.jar[deployablejar] Building deployable-unit-jar: /ho

deploy-ac-locationservice:[slee-management] Install deployable unit file:jars/sip-ac-location-service.jar[slee-management] Activate service SIP AC Loc

22.5.8 Modifying Service Source CodeIf modifications are made to the source code of any of the SIP services, the altered services can be recompiled and

Linphone Setting DescriptionSIP port Default is 5060. Ensure this is different to the SIP RA’s port ifrunning the SLEE and Linphone on the same system

address-of-record = sip:[email protected] bindingsUpdating binding: sip:[email protected] -> sip:[email protected]:

siptest1 siptest2siptest1 siptest2siptest1 siptest2Open Cloud Rhino 1.4.3 Administration Manual v1.1 146

22.6.4 Enabling Debug OutputThe SIP services can write tracing information to the Rhino SLEE logging system via the SLEE Trace Facility.To enable trac

Chapter 23JCC Example Application23.1 IntroductionThe Rhino SLEE includes a sample application that makes use of Java Call Control version 1.1 (JCC 1.

ProviderCallConnection ConnectionAddress AddressFigure 23.1: Object model of a two-party call• Connection: represents the dynamic relationship between

Figure 23.2: Diagrammatic representation of the Call Forwarding Service2. It determines whether the called party has call forwarding enabled, and to w

2.7 Software Development KitThe Open Cloud Rhino SLEE SDK (Figure 2.3) is a JAIN SLEE service development solution and includes:• All software in the

Figure 23.3: Call Attempt(initial-event-select variable="AddressProfile"). So when a “Connection Authorize Call Attempt” event arrives atthe

Figure 23.4: Call Forwarding SBB creation// get profile for service instance’s current subscriberCallForwardingAddressProfileCMP profile;try {// get p

Figure 23.5: OnCallDelivery method executiontrace(Level.FINE, "Forwarding not enabled - ignoring event");return;}// get forwarding addressSt

Figure 23.6: Service finalization. SBB and activity has been removed23.3 Directory ContentsThe base directory for the JCC Examples is $RHINO_HOME/examp

23.4.2 Deploying the Resource AdaptorThe Ant build script$EXAMPLES/build.xmlcontains build targets for deploying and undeploying the JCC RA.To deploy

user@host:~/rhino/examples/jcc$ ant undeployjccraBuildfile: build.xmlmanagement-init:[echo] OpenCloud Rhino SLEE Management tasks definedlogin:[slee-m

user@host:~/rhino/examples/jcc$ ant deployjcccallfwdBuildfile: build.xmlmanagement-init:[echo] OpenCloud Rhino SLEE Management tasks definedlogin:[sle

user@host:~/rhino/examples/jcc$ ant undeployjcccallfwdBuildfile: build.xmlmanagement-init:[echo] OpenCloud Rhino SLEE Management tasks definedlogin:[s

[Rhino@localhost (#6)] listprofilespecsProfileSpecification[AddressProfileSpec 1.0, javax.slee]ProfileSpecification[CallForwardingProfile 1.0, Open Cl

The profile is presented in edit mode.To change profiles, the web interface must be in the “edit” mode. The web interface is left in “edit” mode after a

Chapter 3JAIN SLEE Overview3.1 IntroductionThis chapter discusses key principles of the JAIN SLEE 1.0 specification architecture.The SLEE architecture

Note that the Addresses attribute is an array of addresses, hence the enclosing brackets.[Rhino@localhost (#1)] setprofileattributes CallForwardingPro

The component executes in the same JVM as the SLEE therefore the trace components can only be used if the SLEE processcan access a windowing system.23

For example, the default Call Forwarding Profile enables forwarding from address1111to2222. To test this, launch 3 tracecomponents using addresses1111,

1. It starts when receives a JCC event:• CONNECTION_CONNECTED2. It stores the start time in a CMP field.3. The service receives one of the following JC

Figure 23.8: Initial Event in Call Duration ServiceThis service is executed only in the originating party (user A) because we use an initial event sel

Figure 23.9: Call Duration SBB creationpublic void onCallConnected(JccConnectionEvent event,ActivityContextInterface aci) {JccConnection connection =

<event event-direction="Receive"><event-name>CallDisconnected</event-name><event-type-ref><event-type-name> ja

Figure 23.10: Call Disconnected or Call Failed eventsAfter this, the SBB is not interested in any more events, so it detaches from the activity, and,

Chapter 24Customising the SIP Registrar24.1 IntroductionThis section provides a mini-tutorial which shows developers how to use various features of th

24.3 Performing the CustomisationThe following steps should be carried out in order to provide the additional function.1. Backup the existing SIP Regi

• Within the SLEE. For example:– The SLEE emits events to communicate changes in the SLEE that may be of interest to applications running in theSLEE.–

// --- EXISTING CODE ---...URI uri =((ToHeader)request.getHeader(ToHeader.NAME)).getAddress().getURI();String sipAddressOfRecord = getCanonicalAddress

To undeploy all the SIP example applications, including the SIP resource adaptor, run:ant undeployexamplesAt this point, the Ant system has been succe

Appendix AHardware and Systems SupportA.1 Supported Hardware/OS platformsTable A.1 references platforms that Rhino SLEE supports.A.2 Recommended Hardw

PRODUCT Hardware OS JVM Required 3rdParty SoftwareOpen Cloud Rhino Intel x86(Xeon), AMD64(Opteron), Ultra-SPARC III or IVCPULinux 2.4 or2.6,Solaris 9

requirements. Failure testing is the process of validating whether or not the combination of Rhino, Resource Adaptors andApplication displays appropri

Load generation and network element simulation hardware• Single Ulticom Signalware machine with identical RAM, CPU, Hard Disk configuration to Ulticom

Appendix BRedundant NetworkingThis topic describes how to setup redundant networks for the Rhino SLEE so that cluster members can still communicate in

/etc/hosts:...192.168.1.1 rhinohost1-public # Externally visible IP address for rhinohost1192.168.1.2 rhinohost2-public # Externally visible IP addres

rhinohost1:# ifconfig -a...bge0: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 3inet 192.168.1.101 net

B.1.5 Editing the Routing TableFinally we need to add a multicast route so that the traffic is directed to our interface group.Rather than directing al

3.7 ActivitiesAn Activity represents a related stream of events. These events represent occurrences of significance that have occurred on theentity rep

rhinohost1:/etc/rc2.d/S99static_routes:#!/bin/sh# Probe addresses/usr/sbin/route add rhinohost2-bge0 rhinohost2-bge0 -static/usr/sbin/route add rhinoh

Appendix CResource Adaptors and Resource AdaptorEntitiesC.1 IntroductionThe SLEE architecture defines the following resource adaptor concepts:• Resourc

RA entity created activateEntity() deactivateEntity() Inactive Deactivating Activated Figure C.1: Resource Adaptor Entity lifecycle state machineEach

A property name must be one of the configuration properties defined by the resource adaptor. The configuration propertiesdefined by a resource adaptor can

Appendix DTransactionsD.1 IntroductionThis appendix provides a brief overview of transactions and transaction processing systems including the ACID pr

entities, profiles, Activity Context state, and event queues. The transaction that has successfully acquired the exclusive lock ona unit of transacted

When multiple Resource Managers are combined into a single transaction it is commonplace that both Resource Managerssupport a two-phase commit protoco

Appendix EAudit LogsE.1 File FormatThe format for license audit log files is as follows:{CLUSTER_MEMBERS_CHANGED [comma separated node list]}{INSTALLED

INSTALLED_LICENSESThis is logged whenever the set of valid licenses changes. This may occur when a license is installed or uninstalled, when aninstall

E.2 Example Audit LogfileCLUSTER_MEMBERS_CHANGED [102]INSTALLED_LICENSES 2[LicenseInfo serial=106d78577f5,validFrom=Mon Oct 10 11:34:39NZDT 2005,validU

LEGAL NOTICEUnless otherwise indicated by Open Cloud, any and all product manuals, software and other materials available on the OpenCloud website are

Chapter 4Getting Started4.1 IntroductionThis chapter describes the processes required to install, configure and verify an installation of the Rhino SLE

Appendix FGlossaryAdministrator – A person who maintains the Rhino SLEE, deploys services and resource adaptors and provides access to theWeb Console

Primary Component – The group of nodes in a cluster which can process work.Public Key – A certificate containing an aliased asymmetric public key.Priva

– Linux 2.4– Solaris 9– Red Hat Linux 9The Rhino SLEE is supported on the following Java platforms.– Sun 1.4.2_12 or later for Sparc/Solaris and Linux

• The “awk” command utility.$ which awk/bin/awk• The “sed” command utility.$ which sed/bin/sed4.2.2 PostgreSQL database configurationThe Rhino SLEE dep

>./rhino-install.sh -hUsage: ./rhino-install.sh [options]Command line options:-h, --help - Print this usage message.-a - Perform an automated insta

Management Interface JMX Remote Service Port [1202]:This port is used for the Web Console (Jetty) server and providesremote management user interface.

Creating installation directory.Writing configuration to /home/user/rhino/etc/defaults/config/config_variables.I will now generate the keystores used

$ /home/user/rhino/create-node.shChose a Node ID (integer 1..255)Node ID [101]: 101Creating new node /home/user/rhino/node-101Deferring database creat

>cd node-101>./start-rhino.sh -p4.3.2 Starting a NodeSubsequent nodes can be started by executing the$RHINO_NODE_HOME/start-rhino.shshell script

• Or start a node with the-sswitch by issuing the following command.>cd node-101>./start-rhino.sh -sTypically, to start the cluster for the first

• The Command Console can be started by running the following:$ cd $RHINO_HOME$ ./client/bin/rhino-consoleInteractive Management Shell[Rhino (cmd (arg

Contents1 Introduction 11.1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 C

One important configuration element is to make sure thatntpdis configured to slew the time rather than step time. This can beachieved using the-xflag whe

4.7 Installed FilesA listing of the files in a typical Rhino installation and their descriptions is listed below.CHANGELOG - Release notes.client/ - Di

generate-configuration - Script used internally to populate a Node’s working directory with templated configuration files.generate-system-report.sh -

node-XXX/ - Instantiated Rhino node.config/ - Directory containing configuration files.savanna/ - Savanna configuration files.work/ - Rhino working di

milliseconds of each other then they probably have a causal relationship. Also, if there is a time-out in the software somewhere,that time-out may oft

Chapter 5Management5.1 IntroductionAdministration of the Rhino SLEE is done by using the Java Management Extensions (JMX). An administrator can use ei

5.1.2 Command Console InterfaceThe Command Console is a command line shell which supports both interactive and batch file commands to manage andconfigur

2. Installing a Service.3. Uninstalling a Service.4. Uninstalling a Resource Adaptor.5. Creating a Profile.The tutorial sections 1, 2, 3 and 4 provides

5.4.1 Installing an RA using the Web ConsoleTo install a resource adaptor using the Web Console, first open a web browser and direct it tohttps://local

<resource-adaptor-type-binding><resource-adaptor-type-ref><resource-adaptor-type-name>OCSIP</resource-adaptor-type-name><re

4.6 Optional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.6.1 Introduction . . . . .

$ ./client/bin/rhino-consoleInteractive Rhino Management Shell[Rhino@localhost (#0)]Use theinstallcommand to install the deployable unit. Alternativel

Install the Location Service using the install operation.Install the Registrar Service using the install operation.View the Registrar Service has been

5.5.2 Installing a service using the Command ConsoleTo perform the installation using the Command Console in interactive mode;$ ./client/bin/rhino-con

service please see the Open Cloud SIP Users Guide.5.6 Uninstalling a ServiceThe operations used in this example for uninstalling the registrar applica

Remove the Registrar and Location Service deployable units.5.6.2 Uninstalling a Service using the Command ConsoleThe following steps show how to unins

5.7.1 Uninstalling an RA using the Web ConsoleThe activities are done using theResource Management MBean.We deactivate the resource adaptor entity usi

5.8 Creating a ProfileThis example explains how to create a Call Forwarding Profile which is used by the Call Forwarding Service.Before creating the pro

The Profile MBean can be in two modes: viewing or editing. The operations available on the profile give some hint as to whichmode that profile is in. If

After editing the values, clickapplyAttributeChanges(this will parse and check the attribute values). Then clickcommitProfileto commit the changes.If

Changes made to the profile via the management interfaces are dynamic. The SBBs that implement the example Call Forwardingservices will retrieve the pr

7 Export and Import 517.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517.2

[Rhino (cmd (args)* | help (command)* | bye) #1] createProfile CallForwarding ForwardingProfileCreated profile CallForwarding/ForwardingProfileConfigur

• Stopped to Starting: The Rhino SLEE has no operations to execute.• Stopped to Does Not Exist: The Rhino SLEE processes shutdown and terminate gracef

Chapter 6Administrative Maintenance6.1 IntroductionA system administrator must ensure that the Rhino SLEE maintains peak operational performance. The

the administrator should narrow their search results by applying-node,-cb,-ca, and-raparameters. In the following examplethe administrator searches fo

Table 6.2 contains a summary of the fields returned by getActivityInfo:Field DescriptionpkeyThe Activity’s primary key – uniquely identifies this activi

6.2.3 Inspecting SBBsAdministrators may also search for and query for information about SBB entities. The SBB inspection commands work in thesame way

Field DescriptionpkeyThe SBB entity’s primary key. This identifies the SBB withinits service and SBB component typeparent-pkeyThe pkey of the SBBs pare

SBB EntitiesTheremoveAllSBBscommand accepts a service component ID and will immediately and forcibly remove all SBB entitiesbelonging to that service.

• A new database name will be needed; otherwise the existing database will be overwritten by the new cluster. The existingPostgreSQL installation can

6.4 Backup and RestoreDuring normal operation, all SLEE management and profile data in its own in-memory distributed database. The memorydatabase is fa

12.6.2 Command Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8113 Notification System Configuration

Chapter 7Export and Import7.1 IntroductionThe Rhino SLEE provides administrators and programmers with the ability to export the current deployment and

7.2 Exporting StateIn order to use the exporter, the Rhino SLEE must be available and ready to accept management commands. The exporter isinvoked usin

7.3 Importing StateTo import the state into a Rhino SLEE, execute the ant script in the directory created by the exporter.user@host:~/rhino/rhino_expo

7.4 Partial ImportsA partial import is where only some of the import management operations are executed.This is useful when only deployable units are

Note: The import script will ignore any existing components. It is recommended that the import be run against a RhinoSLEE which has no components depl

Chapter 8Statistics and Monitoring8.1 IntroductionThe Rhino SLEE provides monitoring facilities for capturing statistical performance data about the c

Parameter Set Type Tunable ParametersObject Pools Object Pool SizingStaging Threads Staging ConfigurationMemory Database Sizing Memory Database Size li

$ /home/user/rhino/client/bin/rhino-stats -l EventsParameter Set Type: EventsDescription: Event statsCounter type statistics:Name: Label: Description:

format of statistics output:•-Rwill output raw (single number) timestamps.•-Cwill output comma seperated statistics.•-qwill suppress printing of non-s

Figure 8.1: Creating a Quick GraphFigure 8.2: Creating a Graph with the WizardOpen Cloud Rhino 1.4.3 Administration Manual v1.1 60

18 Application Environment 10418.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 8.3: Selecting Parameter Sets with the Wizard• Load an existing graph configuration from a file. This allows the user to select a previously save

Figure 8.4: Adding Counters with the WizardFigure 8.5: Naming a Graph with the WizardOpen Cloud Rhino 1.4.3 Administration Manual v1.1 62

Figure 8.6: A Graph created with the Wizard2. Or if the client application is already running, by selecting option 4 in the graph creation wizard – “L

Chapter 9Web Console9.1 IntroductionThe Rhino SLEE Web Console is a web application that provides access to management operations of the Rhino SLEE. U

9.2.2 Managed ObjectsThe main page of the Web Console (see Figure 9.1) groups the management beans into several categories:Figure 9.1: Web Console Mai

Clicking on the "Logout" link will end the current session and redisplay the login screen.9.2.4 Interacting with Managed ObjectsThis section

• The Web Console web application archive (web-console.war) contains the J2EE web application itself, consisting ofservlets, static resources (images,

9.4 Configuration9.4.1 Changing Usernames and PasswordsTo edit or add usernames and passwords for accessing Rhino with the Web Console, edit either$RHI

9.5.1 Secure Socket Layer (SSL) ConnectionsThe HTTP server creates encrypted SSL connections using a certificate in the web-console.keystore file. This

Chapter 10Log System Configuration10.1 IntroductionThe Rhino SLEE uses the Apache Log4J logging architecture (http://logging.apache.org/) to provide lo

22.5.7 Removing the Proxy Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14222.5.8 Modifying Service Source C

Log Level DescriptionFATALOnly error messages for unrecoverable errors are produced (not recommended).ERROROnly error messages are produced (not recom

>cd $RHINO_HOME>./client/bin/rhino-console[Rhino@localhost (#1)] help createfileappendercreateFileAppender <appender-name> <filename>

Figure 10.1: Creating a file appenderTo add an AppenderRef so that logging requests for the "savanna.stack" logger key are forwarded to the F

There are also Web Console commands for setting additivity for each logger key and for setting levels as in Figure 10.3.Figure 10.3: Other Logging Adm

Chapter 11AlarmsAlarms are described in the JAIN SLEE 1.0 Specification and are faithfully implemented in the Rhino SLEE. Alarms can beraised by variou

[Rhino@localhost (#28)] listactivealarmsAlarm 56875565751424514 (Node 101, 07-Dec-05 16:44:05.435): Major[resources.cap-conductor.capra.noconnection]

• TheclearAlarmsbutton will clear all alarms in that category.• TheexportAlarmTableAsNotificationsbutton will export all alarms as JMX notifications. T

Chapter 12Threshold Alarms12.1 IntroductionTo supplement the standard alarms raised by Rhino, an administrator may configure additional alarms to be ra

For parameter set type descriptions and a list of available parameter sets use -l <type name> option$ client/bin/rhino-stats -l "System Inf

12.6 Creating RulesRules may be created using either the Web Console or using the Command Console with XML files. The following sectionsdemonstrate how

C Resource Adaptors and Resource Adaptor Entities 182C.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The alarm type and message is set with thesetAlarmoperation.Finally, the rule is activated using the activateRule operation. Once the rule is active i

[Rhino@localhost (#1)] getconfig threshold-rules rule/low_memory<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE rhino-thr

Chapter 13Notification System Configuration13.1 IntroductionThe Rhino SLEE supports notifications as a mechanism for external management clients to be no

public void setSbbContext( SbbContext context ) {this.context =try {final Context c = (Context)new InitialContext().lookup("java:comp/env/slee&qu

Chapter 14Licensing14.1 IntroductionThis chapter explains how to use licenses and the effects licenses have on the running of the Rhino SLEE.In order

The current functions that are used by the Rhino family of products are:“Rhino” – The function used by the production Rhino build for its core functio

14.2.4 Management InterfaceThese are performed via the Web Console and the Command Console. A description of managing a license using the CommandConso

Chapter 15Security Configuration15.1 IntroductionSecurity in the JAIN SLEE is an essential component of the Rhino SLEE architecture. It provides access

Nb. This configuration file is subject to the variable substitution applied to configuration files (replacement of@RHINO_HOME@, etc).The configuration file

<mlet enabled="true"><classpath><jar-url>@FILE_URL@@RHINO_BASE@/lib/jmxr-adaptor.jar</jar-url><jar-url>@FILE_U