Cloud CM-IPMP Instrukcja Naprawy Strona 56
- Strona / 201
- Spis treści
- BOOKMARKI
Oceniono. / 5. Na podstawie oceny klientów
Field Description
pkey
The SBB entity’s primary key. This identifies the SBB within
its service and SBB component type
parent-pkey
The pkey of the SBBs parent SBB
(only applies to child SBBs)
convergence-name
The convergence name generated by the SLEE when
the SBB entity was created. Examining this field is often useful for
debugging applications that use custom convergence name methods
creating-node-id
The cluster node that created this SBB. This
field only has meaning for non-replicated SBBs - for non-replicated SBBs
only the creating node can access the SBB.
Replicated SBBs can be accessed by any node in the cluster
creation-time
The time at which the SBB entity was created.
priority
Event delivery priority of the SBB.
replicated
Replicated flag. This flag will be true only for SBBs
belonging to replicated services.
sbb-component-id
The component ID of the SBBs SBB component.
service-component-id
The component ID of the SBBs encapsulating
service component.
attached-activities
A list of all activities to which the SBB is attached.
Table 6.3: Fields returned by
getSBBInfo
6.2.4 Removing SBB Entities
The administrator may decide to remove an SBB using the
removeSBB
command. Like the
getSBBInfo
command the
removeSBB
command takes the service component id, the SBB component ID and the SBB entity ID as arguments:
[Rhino@localhost (#1)] removeSbb HA\ PingService\ 1.0,\ Open\ Cloud HA\ PingSbb\ 1.0,\ Open\ Cloud 101:8372508:1
[Rhino@localhost (#1)] findsbbs -service HA\ PingService\ 1.0,\ Open\ Cloud -creates-before 1H
pkey creation-time parent-pkey replicated sbb-component-id service-component-id
-------------- ------------------ ------------ ----------- -------------------------- ------------------------------
102:8578700:2 20050418 10:59:55 false HA PingSbb^Open Cloud1.0 HA PingService^Open Cloud1.0
102:8578700:0 20050418 10:59:47 false HA PingSbb^Open Cloud1.0 HA PingService^Open Cloud1.0
102:8578700:1 20050418 10:59:51 false HA PingSbb^Open Cloud1.0 HA PingService^Open Cloud1.0
3 rows
6.2.5 Removing All
Occasionally it is necessary to remove all Activities belonging to a Resource Adaptor or all SBBs in a particular Service. Typi-
cally, an administrator would do this so that a Resource Adaptor or Service can be deactivated for upgrading or reconfiguration.
Under normal conditions these actions would be performed automatically by allowing existing activities and SBBs to drain over
time. Rhino SLEE provides housekeeping commands to forcibly speed up the draining process, although these are to be used
with extreme care on production systems because they will interrupt service for any existing network activities belonging to the
Resource Adaptor or Services.
Activities
The
removeAllActivities
command will remove all activities belonging to a particular Resource Adaptor entity. The activi-
ties are not removed immediately in order to prevent a possible overload being caused by processing a large number of activity
end events all at once, instead the targeted activities are marked as ending and will be ended by the next pass of the query
liveness scan. Typically with default settings, the query liveness scan would rescan within 3 - 5 minutes.
Open Cloud Rhino 1.4.3 Administration Manual v1.1 47
- 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.042 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji