Log:
Assessments - 0, GPA: 0 ( )

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

Fabricante : HP
Arquivo Tamanho: 640.33 kb
Arquivo Nome :
Língua de Ensino: enfr
Ir para baixar



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

Facilidade de uso


protocol called GIOP. GIOP messages can be sent over virtually any data transport protocol, such as TCP/IP, the TS/MP
Pathsend interface, the NonStop Himalaya file system, and many others. To ensure out-of-the-box interoperability between
ORB products, the IIOP specification requires that ORBs send GIOP messages over TCP/IP connections because TCP/IP is
the standard connection-oriented transport protocol for the Internet. To put it very simply, GIOP + TCP/IP = IIOP.
Objects publish their identities and locations in the form of object references. The CORBA 2.0 specification dictates a
common format for object references exchanged over IIOP, called IOR (Interoperable Object Reference) format. An IOR
contains one or more profiles. Each profile describes how a client object can contact and send requests to the object using a
particular protocol. For interoperability between ORBs provided by different vendors, an IOR should contain an IIOP profile
to ensure that wherever that reference goes, any CORBA-compliant ORB can locate the object and send requests to it. The
IIOP profile contains the Internet address of the objects server and a key value used by the server to find the specific object
described by the reference.
Object references can be converted into character strings, which can be published arbitrarily, like URLs, in email messages,
files, databases, directories, and so on. Any CORBA-compliant application can convert the string into an IOR and use it to
locate and invoke the object. Alternatively, the IOR can be obtained from the Naming service.
When a client program built with one ORB vendors product needs to talk to an object in a server built with another ORB
vendors product, the client program opens a TCP/IP connection to the server and sends one or more IIOP requests to the
server. The ORB component linked into the server locates or activates the object specified in the request and invokes the
appropriate method on the object. The fact that the object is not built with the same ORB product is invisible to the client.
CORBA/IIOP is platform-independent. CORBA ORBs interoperate without regard to vendor origin, making CORBA/IIOP
the truly ideal solution for the Internet.
NonStop CORBA 2.3 can use three transport protocols when communicating between objects. All three use the OMGs
GIOP and each can be represented as a profile within an IOR. These three protocols are:
IIOP, the standard messaging protocol utilizing TCP/IP, used for all remote messages to platforms other than NonStop
q
Himalaya platforms.
GIOP over TS/MP (Pathway) inter-ORB protocol implementation. This protocol is used when accessing objects whose
q
server is controlled by TS/MP.
GIOP over Guardian file system inter-ORB protocol Implementation). This protocol is used when client objects wish
q
to communicate with objects whose server is either running as a stand-alone process or as stateful objects managed by
TS/MP.
GIOP Over TS/MP Protocol
Compaq strongly recommends configuring your production servers with the GIOP over TS/MP protocol, because this
protocol leverages the features of process management, process persistence, load balancing, and scalability.
A server that supports TS/MP can be configured as either a single process or as a group of processes within a server pool. In
either case, client messages and server replies are sent using TS/MP interprocess communication (IPC) when both client and
server reside on the NonStop Himalaya platform.
GIOP over TS/MP is a protocol internal to NonStop CORBA. All inter-ORB communication can use this NonStop CORBA
protocol, however, all heterogeneous ORB communication must still take place through the TCP/IP protocol used by IIOP.
GIOP Over Guardian File System Protocol
A server that supports only the file-system protocol can be configured either as a stand-alone process or as a named process
managed by TS/MP. The NonStop CORBA system manages client access to file-system servers using interprocess
communication (IPC). Clients must use the file-system protocol to talk to a server that supports only this protocol.

...

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

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



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





categorias