RPC -WR5441 Bedienungsanleitung PDF herunterladen

- 1 -

1. DCE Remote Procedure Call

The DCE Remote Procedure Call (RPC) facility is a network protocol used in distributed systems. RPC is

modeled after the local procedure call found in most programming languages, but the called procedure is

executed in a different process from that of the caller, and is usually executed on another machine. The

RPC facility makes the construction of distributed systems easier because developers can focus on the

fundamentals of building distributed applications, instead of the underlying communication mechanisms.

Making a remote procedure call involves ﬁve different bodies of code:

• the client application

• the client stub

• the RPC runtime library

• the server stub

• the server application

The client and server stubs are created by compiling a description of the remote interface with the DCE

Interface Deﬁnition Language (IDL) compiler. The client application, the client stub, and one instance of

the RPC runtime library all execute in the caller machine; the server application, the server stub, and

another instance of the RPC runtime library execute in the called (server) machine.

1.1 Outline of a Remote Procedure Call

When a client application makes a remote procedure call, it actually invokes a local procedure in the client

stub. The client stub places a speciﬁcation of the called procedure and its arguments into one or more

packets and asks the RPC runtime library to transmit them to the machine that actually executes the

procedure. The process by which a stub converts local application data into network data and packages the

network data into packets for transmission is called marshalling.

When the RPC runtime library for the server receives these packets, it passes them to the server stub. The

server stub extracts the procedure arguments from these packets and makes a local call to the indicated

procedure. The process by which a stub disassembles incoming network data and converts it into

application data is called unmarshalling.

When this local call returns to the server stub, the server stub marshals the data. It places the results (the

return code and output parameters) into one or more packets and asks the RPC runtime library to transmit

them back to the client.

When the client RPC runtime library receives these packets, it passes them on to the client stub for

unmarshalling. The client stub extracts the results and returns them to the client.

In addition to handling all communications between client and server applications, the RPC runtime

library provides the following utilities:

• An interface that lets applications access various name servers (which can be used to locate various

network resources).

• Management services such as monitoring servers, monitoring runtime operations, and stopping servers.

1.2 Considerations and Dependencies

DCE RPC internally uses a vendor-provided threading facility (POSIX Pthreads). There is wide variation

in the completeness and transparency of the various Pthread implementations provided by vendors. The

limitations of a given Pthread implementation are inherited by any application that uses DCE RPC,

including applications that unknowingly use libraries that internally happen to use DCE RPC.

The DCE RPC runtime has internal threads that need to run in a timely fashion for the runtime to operate

correctly. Therefore, the application or Pthreads implementation must neither perform nor permit

operations that block the entire process. This restriction is relevant only if you are using a threads

implementation other than DCE Threads. Refer to the platform’s or vendor’s Pthread release notes to

1 2 3 4 5 6 ... 29 30

Inhaltsverzeichnis

Seite 1

- 1 -1. DCE Remote Procedure CallThe DCE Remote Procedure Call (RPC) facility is a network protocol used in distributed systems. RPC ismodeled after

Seite 2

- 10 -dce-root-dir/dce/src/rpc/sys_idl/idlbase.hheader ﬁle, conditionally control various aspects of the IDL API:• IDL_NO_PROTOTYPESDeﬁne IDL_NO_PROTO

Seite 3 - #if deﬁned(__PLATFORM__)

- 11 -RPC_SS_THREADS_CONDITION_CREATERPC_SS_THREADS_CONDITION_DELETERPC_SS_THREADS_CONDITION_SIGNALRPC_SS_THREADS_CONDITION_TRPC_SS_THREADS_CONDITION_

Seite 4 - • BRANCHSTRING

- 12 -If you do not have such an interface or cannot get the number, you will have to produce your own wayto generate a unique number. IEEE will sell

Seite 5 - #include <dce/%s>\n

- 13 -This currently governs including certain Internet include ﬁles. See ipnaf.h and twr*.c ﬁles.ATFORK_SUPPORTEDIf a fork handler is available, this

Seite 6 - #deﬁne globalref extern

- 14 -Not used, although present in:dce-root-dir/dce/src/rpc/runtime/TARGET_MACHINE/sysconf.hRPC_NLS_FORMATNot used, although present in:dce-root-dir/

Seite 7 - • USE_DEFAULT_MACROS

- 15 -The code that enables remote endpoint access is still present in the source, however, and it can be enabledor disabled by deﬁning or undeﬁning t

Seite 8

- 16 -The DSM does not currently itself provide mutual exclusion, although it must be used in such a context(the caller is currently assumed to do the

Seite 9

- 17 -3. Building and LinkingThedce-root-dir/dce/src/rpc/runtime/Makeﬁlemay be used to conﬁgure libnck.a for various combinations of network protocol

Seite 10

- 18 -4. Setup, Testing, and VeriﬁcationMake sure that the rpcd endpoint map service is running.Change to the/opt/dce1.1/bindirectory and enterrpcdto

Seite 11 - • uuidsys.c

- 19 -See thedce-root-dir/dce/src/test/rpc/runtime/perf/READMEﬁle for further information, including information about several scripts that can be use

Seite 12 - • machine/sysconf.h

- 2 -determine what limitations the implementation has.You should also instruct users of any library you develop that uses RPC to refer to the vendor’

Seite 13 - • AUTH_KRB_CN

- 20 -and terminate.principal Speciﬁes the principal name of the server to use when authenticating remoteprocedure calls. The content of the name and

Seite 14

- 21 --D This optional parameter speciﬁes the default level of debug output.-i This optional parameter causes statistics to be dumped at the end of th

Seite 15

- 22 -2ServerperformsauthorizationcheckingusingtheclientDCEprivilegeattribute certiﬁcate (PAC) information sent to the server with eachremote procedur

Seite 16

- 23 -7Callunregisteredserverinterface8Forwardingtest9 Exception test10 Slow call11 Shutdown server12 Callback (Note: This test is not supported.)13 G

Seite 17

- 24 -network_address is the network address of the server, and port is the portthe server is listening to.passesSpeciﬁes the number of times to run t

Seite 18

- 25 -5. RPC Runtime Output and Debugging OutputThe RPC component outputs server information of all kinds via the DCE serviceability component. Thefo

Seite 19 - [-v {0

- 26 -• TEXTFILEWrite these messages as human-readable text• FILEEquivalent to TEXTFILE• DISCARDDo not record messages of this severity level• STDOUTW

Seite 20

- 27 -Speciﬁes that:• Fatal error messages should be sent to the console.• Warnings should be discarded.• Notices should be written both to standard e

Seite 21

- 28 -recv RPC receive messagesdg_state RPC DG state messagescancel RPC cancel messagesorphan RPC orphan messagescn_state RPC CN state messagescn_pkt

Seite 22

- 29 -that you specify. RPC_SUPPORTED_PROTSEQSis an environment variable tested at RPC startup bycode in:dce-root-dir/dce/src/rpc/runtime/cominit.cIt

Seite 23

- 3 -2. PortingOSFTMDCE Version 1.1 contains DCE RPC code ported to the reference platforms listed in Chapter 1 ofthis guide. As you port RPC to a di

Seite 24

- 30 -6. Some RPC Questions and AnswersThis section contains several RPC questions and answers that have arisen during DCE porting andapplication dev

Seite 25

- 4 -• message.cThis ﬁle contains a layer of message catalog routines speciﬁc to the IDL compiler. If you do not have amessage catalog system, you mus

Seite 26 - WARNING:DISCARD:

- 5 -#deﬁne HASPOPEN if your system supports the popen( ) call.IDL_PROTOTYPESDeﬁned if IDL should use prototypes.IDL_VERSION_TEXTVersion string for ID

Seite 27

- 6 -USER_INCLUDE_TEMPLATEis deﬁned as:#include <%s>2.1.2 Deﬁnitions for lex and yacc The IDL compiler uses lex and yacc to parse interface deﬁ

Seite 28

- 7 -TABLE 2. idlbase.h and <TARGET_MACHINE>/ndrtypes.h Deﬁnes__ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Seite 29 - TSEQS ncadg_ip_udp

- 8 -rpc_marshall_long_intrpc_marshall_short_ﬂoatrpc_marshall_short_intrpc_marshall_small_intrpc_marshall_uhyper_intrpc_marshall_ulong_intrpc_marshall

Seite 30

- 9 -rpc_unmarshall_ushort_intrpc_unmarshall_usmall_intrpc_unmarshall_v1_enum• USE_DEFAULT_MP_REPControls the deﬁnition of a type and the macros which

Kommentare zu diesen Handbüchern

Keine Kommentare

RPC -WR5441 Bedienungsanleitung

Stöbern Sie online oder laden Sie Bedienungsanleitung nach Server RPC -WR5441 herunter. 1. DCE Remote Procedure Call The DCE Remote [en] [fr] Benutzerhandbuch

Inhaltsverzeichnis

Kommentare zu diesen Handbüchern