Cloud CM-IPMP Instrukcja Naprawy Strona 53
- Strona / 201
- Spis treści
- BOOKMARKI
Oceniono. / 5. Na podstawie oceny klientów
the administrator should narrow their search results by applying
-node
,
-cb
,
-ca
, and
-ra
parameters. In the following example
the administrator searches for activities belonging to the resource adaptor entity
TestRA
.
[Rhino@localhost (#1)] findactivities
pkey handle ra-entity replicated submission-time update-time
------------------------- ---------------------------------------- --------------- ----------- ----------------- ------------------
65.0.4E8BF.1.2A567636 ServiceActivity[HA PingService 1.0, Open Cloud] Rhino internal true 20050418 10:52:54 20050418 10:52:54
65.2.4E8BF.0.2EA48 SAH[switchID=8756,connectionID=4,address=1] TestRA false 20050418 10:59:53 20050418 11:01:50
66.2.4E98A.0.2EA49 SAH[switchID=8756,connectionID=5,address=1] TestRA false 20050418 10:59:55 20050418 11:02:12
66.0.4E98A.0.2EA45 SAH[switchID=8756,connectionID=1,address=1] TestRA false 20050418 10:59:47 20050418 11:02:12
66.DE.4E98A.0.2EC08 SAH[switchID=8756,connectionID=452,address=1] TestRA false 20050418 11:11:48 20050418 11:12:25
66.F8.4E98A.0.2EC39 SAH[switchID=8756,connectionID=501,address=1] TestRA false 20050418 11:12:37 20050418 11:12:37
65.F5.4E8BF.0.2EC26 SAH[switchID=8756,connectionID=482,address=1] TestRA false 20050418 11:12:17 20050418 11:12:17
65.F3.4E8BF.0.2EC24 SAH[switchID=8756,connectionID=480,address=1] TestRA false 20050418 11:12:15 20050418 11:12:15
65.F8.4E8BF.0.2EC2E SAH[switchID=8756,connectionID=490,address=1] TestRA false 20050418 11:12:26 20050418 11:12:26
66.1.4E98A.0.2EA47 SAH[switchID=8756,connectionID=3,address=1] TestRA false 20050418 10:59:51 20050418 11:02:12
65.F0.4E8BF.0.2EC1C SAH[switchID=8756,connectionID=472,address=1] TestRA false 20050418 11:12:08 20050418 11:12:08
65.F6.4E8BF.0.2EC2B SAH[switchID=8756,connectionID=487,address=1] TestRA false 20050418 11:12:23 20050418 11:12:23
65.ED.4E8BF.0.2EC16 SAH[switchID=8756,connectionID=466,address=1] TestRA false 20050418 11:12:01 20050418 11:12:25
66.EF.4E98A.0.2EC29 SAH[switchID=8756,connectionID=485,address=1] TestRA false 20050418 11:12:21 20050418 11:12:21
65.FD.4E8BF.0.2EC3A SAH[switchID=8756,connectionID=502,address=1] TestRA false 20050418 11:12:38 20050418 11:12:38
65.E3.4E8BF.0.2EC05 SAH[switchID=8756,connectionID=449,address=1] TestRA false 20050418 11:11:45 20050418 11:12:20
66.ED.4E98A.0.2EC27 SAH[switchID=8756,connectionID=483,address=1] TestRA false 20050418 11:12:18 20050418 11:12:18
....
100 rows
The 100 rows returned represents only some of the available activities. In order to find activities of interest, the search must
narrowed with more specific arguments.
A common use of this facility would be to find activities which have become stale. The Rhino SLEE performs a periodic liveness
scan. This means that all active activities are scanned and any detected stale activities are ended. However, it is possible that
due to a failure in the network or inside a Resource Adaptor, the liveness scans may not detect and end all stale activities. In
these cases, an administrator must locate and end stale activities manually.
To narrow the search to activities belonging to node 101 (i.e. any activities whose processing node is 101 and are replicated and
non-replicated activities) that are more than 1 hour old, add the parameters
-node 101
and
-cb 1H
:
[Rhino@localhost (#1)] findactivities -ra TestRA -node 101 -cb 1H
pkey handle ra-entity replicated submission-time update-time
------------------------- ---------------------------------------- ---------- ----------- ------------------ ------------------
65.1.2E8BF.0.2EA46 SAH[switchID=8756,connectionID=2,address=1] TestRA false 20050418 10:59:49 20050418 11:01:50
65.2.2E8BF.0.2EA48 SAH[switchID=8756,connectionID=4,address=1] TestRA false 20050418 10:59:53 20050418 11:01:50
2 rows
Two activities are returned from the search. The administrator may decide to interrogate Rhino for additional information about
one of these activities. This is achieved using the
getActivityInfo
command. This command takes a single parameter – the
Activity’s primary key (from the pkey column in the findActivities result set). To get additional information about the first of
the returned activities:
[Rhino@localhost (#1)] getactivityinfo 65.1.2E8BF.0.2EA46
pkey : 65.1.2E8BF.0.2EA46
ending : false
events-processed : 1
handle : SAH[switchID=8756,connectionID=2,address=1]
processing-node : 101
queue-size : 0
ra-entity : TestRA
eeference-count : 1
replicated : false
sbbs-invoked : 1
submission-time : 20050418 10:59:49
submitting-node : 101
update-time : 20050418 11:01:50
attached-sbbs :
> pkey replicated sbb-component-id service-component-id
> -------------------- ----------- -------------------------- ------------------------------
> 101:8372508:0 false HA PingSbb^Open Cloud1.0 HA PingService^Open Cloud1.0
> 1 rows
events :
no rows
The information returned by the getActivityInfo command is a snapshot of the Activity’s state at the time the command is
executed. Some values (fields pkey, ra-entity, replicated, submission-time, submitting-node, and handle) are fixed for the
lifetime of the activity. Others will change as events are processed on the activity.
Open Cloud Rhino 1.4.3 Administration Manual v1.1 44
- Open Cloud Rhino SLEE 1.4.3 1
- Administration Manual 1
- November 2, 2006 (1838) 2
- Contents 3
- Introduction 10
- The Rhino SLEE Platform 12
- 2.3 Integration 13
- 2.4 Service Development 14
- 2.5 Functional Testing 15
- 2.6 Performance Testing 15
- 2.7 Software Development Kit 16
- JAIN SLEE Overview 17
- 3.3 Event Driven Applications 18
- 3.4 Components 18
- 3.5 Provisioned Data 18
- 3.6 Facilities 18
- 3.7 Activities 19
- 4.2.3 Firewalls 22
- 4.2.4 Unpacking 22
- 4.2.5 Installation 22
- 4.2.6 Unattended Installation 23
- 4.2.7 Configuring a Cluster 23
- 4.2.9 Configuring the Cluster 25
- 4.3 Cluster Lifecycle 26
- 4.3.2 Starting a Node 27
- 4.3.3 Starting a Quorum Node 27
- 4.3.4 Automatic Node Restart 27
- 4.3.5 Starting the SLEE 27
- 4.4 Management Interface 28
- 4.5 Setting the system clock 29
- 4.6 Optional Configuration 30
- 4.7 Installed Files 31
- 4.8 Runtime Files 32
- 4.8.2 Logging output 33
- Management 35
- 5.2 Management Tutorials 36
- 5.3 Building the Examples 37
- 5.5 Installing a Service 40
- 5.6 Uninstalling a Service 43
- 5.8 Creating a Profile 46
- 5.9 SLEE Lifecycle 50
- 5.9.4 The Stopping State 51
- 5.9.2 The Starting State 51
- 5.9.3 The Running State 51
- Administrative Maintenance 52
- 6.2.2 Removing Activities 54
- 6.2.3 Inspecting SBBs 55
- 6.2.4 Removing SBB Entities 56
- 6.2.5 Removing All 56
- 6.3 Upgrading a Cluster 57
- 6.3.3 Deploying State 58
- 6.4 Backup and Restore 59
- Export and Import 60
- 7.2 Exporting State 61
- 7.3 Importing State 62
- 7.4 Partial Imports 63
- Statistics and Monitoring 65
- 8.2 Performance Implications 66
- 8.3 Console Mode 66
- 8.3.1 Useful output options 67
- 8.4 Graphical Mode 68
- Web Console 73
- 9.2.2 Managed Objects 74
- 9.2.3 Navigation Shortcuts 74
- 9.3 Deployment Architecture 75
- 9.3.2 Standalone Web Console 76
- 9.4 Configuration 77
- 9.5 Security 77
- 9.5.2 Declarative Security 78
- 9.5.3 JAAS 78
- Log System Configuration 79
- 10.3 Logging Configuration 80
- 10.3.2 Web Console Logging 81
- Chapter 11 84
- 11.2.2 Web Console 85
- Threshold Alarms 87
- 12.5 Types of Rule Conditions 88
- 12.6 Creating Rules 89
- 12.6.2 Command Console 90
- Chapter 13 92
- 13.3.1 Configuration 93
- Licensing 94
- 14.2 Alarms 95
- 14.2.4 Management Interface 96
- 14.2.5 Audit Logs 96
- Security Configuration 97
- 15.3 Network Connections 98
- 15.4 Signing Deployable Units 99
- 15.5 Key Stores 100
- 15.6 Transport Layer Security 100
- 15.7 JAAS Configuration 101
- Performance Tuning 103
- 16.2.3 Tuning Recommendations 104
- 16.2.1 Configuration 104
- 16.2.2 Stage Tuning 104
- 16.3 Object Pool Configuration 105
- 16.4 Fault Tolerance 106
- Clustering 109
- 17.3 Scenarios 110
- 17.4 Configuration Parameters 111
- Application Environment 113
- 18.2.2 Concurrency Control 114
- 18.3 Application Configuration 115
- 18.5.4 Example 119
- 18.6 Application Fail-Over 120
- 18.6.2 Management Interface 121
- Database Connectivity 122
- 19.3 Configuration Example 123
- 19.4 SBB use of JDBC 124
- 19.4.1 SQL Programming 125
- J2EE SLEE Integration 127
- PostgreSQL Configuration 131
- 21.4 TCP/IP Connections 132
- 21.5 Access Control 132
- SIP Example Applications 138
- 22.2 System Requirements 139
- 22.3 Directory Contents 139
- 22.4 Quick Start 139
- 22.4.2 Building and Deploying 140
- 22.5 Manual Installation 144
- 22.6 Using the Services 152
- 22.6.4 Enabling Debug Output 156
- JCC Example Application 157
- 23.2.1 Resource Adaptor 158
- 23.2.3 Service Logic 160
- 23.3 Directory Contents 163
- 23.4 Installation 163
- 23.6.1 Trace Components 170
- 23.6.3 Creating a Call 171
- 23.7 Call Duration Service 172
- Customising the SIP Registrar 178
- 24.4 Extending with Profiles 181
- Hardware and Systems Support 182
- A.2.4 Application Example 184
- Redundant Networking 186
- Entities 191
- C.3 Configuration Properties 192
- C.4 Entity Binding 193
- Transactions 194
- D.3.3 Summary 195
- D.4.3 Commit Protocols 196
- Audit Logs 197
- E.2 Example Audit Logfile 199
- Glossary 200
© 2020, manymanuals.pl. Wszelkie prawa zastrzeżone. | 0.114 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji