Log:
Assessments - 0, GPA: 0 ( )

Instruções de Operação HP, Modelo HP NonStop G-Series

Fabricante : HP
Arquivo Tamanho: 1.18 mb
Arquivo Nome :
Língua de Ensino: ennn
Ir para baixar



por este dispositivo também tem outras instruções :

Facilidade de uso


Connection Modes
Jolt supports notification receipt for clients working in either connection-retained or connection-less modes of operation.
Connection-retained clients receive all notifications. Jolt clients working in connection-less mode will receive notifications while they
have an active network connection to the Jolt Session Handler (JSH). When the network connection is closed, the JSH logs and drops
notifications destined for the client. Jolt clients operating in a connection-less mode will not receive unsolicited messages or notifications
while they do not have an active network connection. All messages received during this time are logged and discarded by the JSH.
Acknowledged Notifications
Connection mode notification handling includes acknowledged notifications for Jolt 1.1 clients in a NonStop TUXEDO environment. If a
JSH receives an acknowledged notification for a client and the client does not have an active network connection, the JSH logs an error
and return a failure acknowledgment to the notification.
Notification Data Buffers
When a client receives notification, it is accompanied by a data buffer. The data buffer can be of any TUXEDO data buffer type. Jolt
clients (i.e., the handler) will receive these buffers as a JoltMessage object and should use the appropriate JoltMessage class get*()
methods to retrieve the data from this object.
The Jolt Repository does not need to have the definition of the buffers used for notification. However, the Jolt client application
programmer will need to know field names beforehand.
The Jolt system does not provide functionality equivalent to tptypes() in TUXEDO, so in effect a Jolt 1.1 client is limited to receiving a
"known" buffer type. For FML and VIEW buffers, the data will be accessed using the get*() methods with the appropriate field name, for
example, enter:
getIntDef ("ACCOUNT_ID", -1);
For STRING and CARRAY buffers, the data will be accessed by the same name as the buffer type, e.g.,:
getStringDef ("STRING", null);
getBytesDef ("CARRAY", null);
STRING and CARRAY buffers contain only a single data element: this complete element is returned in the get*() methods above.
TUXEDO Event Subscription
TUXEDO brokered event notification allows TUXEDO programs to post events without needing to know what other programs are
supposed to receive notification of an event's occurrence. The Jolt event notification allows Jolt client applications to subscribe to
TUXEDO events that are broadcast or posted using the TUXEDO tpnotify() or tpbroadcast() calls.
Jolt clients are only able to subscribe to events and notifications that are generated by other components in TUXEDO (such as a TUXEDO
Service or Client). Jolt 1.1 clients are not able to send events or notifications.
Supported Subscription Types
Jolt 1.1 only supports notification types of subscriptions. The Jolt onReply() method is called when a subscription is fulfilled. The Jolt 1.1
API does not support dispatching a service routine or enqueueing a message to an application queue when a notification is received.
Subscribing to Notifications
If a Jolt client subscribes to a single event notifications, the client receives both unsolicited messages and event notification. Subscribing to
an event implicitly enables unsolicited notification. This means that if the application creates a JoltUserEvent object for Event "X", the
client will automatically receive notifications directed to it as a result of tpnotify() or tpbroadcast().
Note
This is NOT the recommended method for enabling unsolicited notification--if you want
unsolicited notification, the application should explicitly do so (as described in the
JoltUserEvent class). The reason for this is explained in the following unsubscribe section.
Unsubscribing from Notifications
To stop subscribing to event notifications and/or unsolicited messages, you need to use the JoltUserEvent unsubscribe method. In Jolt,
disabling unsolicited notifications with an unsubscribe method does not turn off all subscription notifications. This differs from TUXEDO.
In TUXEDO the use of tpsetunsol() with a NULL handler turns off all subscription notifications.
When unsubscribing, the following considerations apply:

...

Este manual também é adequado para os modelos :
Computadores - HP NonStop L-Series (1.18 mb)

Escreva a sua própria avaliação do dispositivo



Mensagem
Seu nome :
Introduza os dois dígitos :
capcha





categorias