EntireX	Version 9.7	SEARCH   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

The Broker-internal RPC CIS Server provides the Command and Information Services using the Remote Procedure Call (RPC) protocol.

Two CIS IDL files are available in directory EntireX\etc\idl.

RPC CIS is a complete implementation of the Command and Information Services.

See Broker CIS Data Structures for a description of the CIS API. The names of the fields can also be found in the IDL (with case-insensitive and insignificant modifications).

The service names SAG/ETBCIS/RPCCIS and RPC/RPCCIS/CALLNAT can be used for all versions of the CIS IDLs.

This document covers the following topics:

• Command Service IDL

• Info Service IDL

• Examples

Command Service IDL

The files SagCmdServiceV6.idl to SagCmdServiceV8.idl are contained in directory etc. They provide an interface description of CIS version 6 and above. Brokers with more recent CIS versions are backward compatible down to version 6 via RPC CIS.

File SagCmdServiceV8.idl provides the interface description for all Command Services of CIS version 8.

This section covers the following topics:

• Stucture COMMAND_REQUEST

• Program COMMAND

Stucture COMMAND_REQUEST

struct 'COMMAND_REQUEST' is  /*Broker CIS: command request structure
  define data parameter
  1 Command                (I2)
  1 ObjectType             (I2)
  1 Option                 (I2)
  1 puid                   (B28)
  1 uowid                  (A16)
  1 Topic                  (A96)
  1 uid                    (A32)
  1 Token                  (A32)
  1 ServerClass            (A32)
  1 ServerName             (A32)
  1 ServiceName            (A32)
  1 reserved_etbinfo_v73_2 (A32)
  1 convid                 (A16)
  1 transportId            (A3)
  1 nSequenceNumber        (I4)
  1 cExcludeAttachServers  (I1)
  1 nErrorNumber           (I4)
  end-define

The request structure is described under Command Request Structure. Note also the Command Request Parameter Combinations.

Program COMMAND

Program 'COMMAND':'command' is  /*command request
 define data parameter
 1 CmdRequest      ('COMMAND_REQUEST')  In
 1 Function_Result (I4)                 Out
 end-define

You can call the command service using program COMMAND, with the structure COMMAND_REQUEST as argument. See Command Request Structure. Alternatively, you can enter the functions listed in the table directly:

Notes:

1. Short name as used, for example, by C programs.
2. Long name as used, for example, by Java programs.
3. You cannot execute CSHUTB (cmdShudtownBroker) in a non-secure mode.
4. See Writing Applications: Publish and Subscribe.

The prototypes and source code can be found in the generated files:

Info Service IDL

Files SagInfServiceV6.idl to SagInfServiceV8.idl are contained in directory etc. They provide an interface description of CIS version 6 and above. Brokers with more recent CIS versions are backward compatible down to version 6 via RPC CIS.

File SagInfServiceV8.idl provides the interface description for all Information Services. The following functions are used to receive an unbounded array of the corresponding Broker Information Service.

See also Using Unbounded Arrays.

Structure INFORMATION_REQUEST

struct 'INFORMATION_REQUEST' is  /*CIS: information request
  define data parameter
  1 ObjectType       (I2)
  1 uid              (A32)
  1 puid             (B28)
  1 Token            (A32)
  1 ServerClass      (A32)
  1 ServerName       (A32)
  1 ServiceName      (A32)
  1 convid           (A16)
  1 uowid            (A16)
  1 uowStatus        (I1)
  1 userStatus       (A32)
  1 recvUID          (A32)
  1 recvToken        (A32)
  1 recvClass        (A32)
  1 recvServer       (A32)
  1 recvService      (A32)
  1 Topic            (A96)
  1 publicationId    (A16)
  1 subscriptionType (I2)
  1 conversationType (I2)
  1 level            (I1)
  end-define

The request structure is described under Information Request Structure.

The optional parameter level, which only appears in the Info Service IDL, determines the service used:

• If level=0 the RPC request is passed to the broker-internal service USER-INFO (default).

• If level=1 the RPC request is passed to the service INFO.

Program: INFO

program 'INFO':'info' is  /*all
  define data parameter
  1 InfRequest       ('INFORMATION_REQUEST')   In
  1 InfBroker        ('INFO_BRK'/V)            Out
  1 InfWorker        ('INFO_WRK'/V)            Out
  1 InfService       ('INFO_SV'/V)             Out
  1 InfClient        ('INFO_CS'/V)             Out
  1 InfServer        ('INFO_CS'/V)             Out
  1 InfParticipant   ('INFO_CS'/V)             Out
  1 InfConversation  ('INFO_CV'/V)             Out
  1 InfPSF           ('INFO_PSF'/V)            Out
  1 InfPSFADA        ('INFO_PSFADA'/V)         Out
  1 InfPSFDIV        ('INFO_PSFDIV'/V)         Out
  1 InfPSFFile       ('INFO_PSFFILE'/V)        Out
  1 InfPSFCTree      ('INFO_PSFCTREE'/V)       Out
  1 InfSubscriber    ('INFO_SUBSCRIBER'/V)     Out
  1 InfPublisher     ('INFO_PUBLISHER'/V)      Out
  1 InfPublication   ('INFO_PUBLICATION'/V)    Out
  1 InfTopic         ('INFO_TOPIC'/V)          Out
  1 InfTcp           ('INFO_TCP'/V)            Out
  1 InfSecurity      ('INFO_SECURITY'/V)       Out
  1 InfSsl           ('INFO_SSL'/V)            Out
  1 InfCmdLogFilter  ('INFO_CMDLOG_FILTER'/V)  Out
  1 InfNet           ('INFO_NET'/V)            Out
  1 InfPoolUsage     ('INFO_POOL_USAGE'/V)     Out
  1 InfResourceUsage ('INFO_RESOURCE_USAGE'/V) Out
  1 InfStatistics    ('INFO_STATISTICS'/V)     Out
  1 InfUser          ('INFO_USER'/V)           Out
  1 InfWorkerUsage   ('INFO_WRK_USAGE'/V)      Out
  1 Function_Result  (I4)                      Out
  end-define

You can call the information service using program INFO, with the structure INFORMATION_REQUEST as argument. See Information Request Structure. Depending on the object type, the reply will contain the corresponding INFO_ structure containing one or more records. The variable array contains all available data. No segmentation takes place. Alternatively, you can call directly the functions listed below for the individual object types.

All functions below return the corresponding structure from the information reply structures.

Notes:

1. Short name as used, for example, by C programs.
2. Long name as used, for example, by Java programs.

The prototypes and source code can be found in the generated files:

Examples

The following examples are available:

• .NET CIS Client Example

• Java CIS Client Example

.NET CIS Client Example

The .NET CIS Client Example can be found in the examples directory NetWrapper\Client\SagCisClient.cs. The directory includes the source file SagCisClient.cs and the README.TXT.

Information required to prepare and configure the EntireX Workbench:

• EntireX Workbench.

• Using EntireX Custom Wrappers or

• Using the EntireX Workbench in Command-line Mode.

Information required to to write a .NET CIS Client:

• Writing Applications with the .NET Wrapper.

• Using Unbounded Arrays.

Build steps:

1. Prepare Eclipse.

2. Start Eclipse.

3. Create a new Java Project.

4. Add files SagCmdServiceV8.idl and SagInfServiceV8.idl to the project.

5. Generate the .NET RPC Client from SagCmdServiceV8.idl using the context menu.

6. Generate the .NET RPC Client from SagInfServiceV8.idl using the context menu.

7. Start Visual Studio.

8. Create a new Visual Studio Project. (.NET Console Application).

9. Insert the generated sources SAGCCV8.cs and SAGCIV8.cs.

10. Delete Program.cs.

11. Insert .NET example file SagCisClient.cs to the project.

12. Add Reference (<drive>:\SoftwareAG\common\EntireX\bin\SoftwareAG.EntireX.NETWrapper.Runtime.dll).

13. Build the solution.

14. Start the .NET CIS Client.

Java CIS Client Example

The Java CIS Client Example can be found in the examples directory EntireX\Examples\JavaWrapper\Client\SagCisService\mainSagCisClient.java. This directory includes the source file mainSagCisClient.java and the README.TXT.

Information required to prepare and configure the EntireX Workbench:

• EntireX Workbench.

• Using EntireX Custom Wrappers or

• Using the EntireX Workbench in Command-line Mode

Information required to to write a Java CIS Client:

• Writing Applications with the Java Wrapper

Build steps:

1. Prepare Eclipse.

2. Start Eclipse.

3. Create a new Java Project.

4. Add files SagCmdServiceV8.idl and SagInfServiceV8.idl to the project.

5. Add source file mainSagCisClient.java to the project.

6. Generate the Java RPC Client from SagCmdServiceV8.idl using the context menu.

7. Generate the Java RPC Client from SagInfServiceV8.idl using the context menu.

8. Build the Java CIS Client project.

9. Start the Java CIS Client.

www.softwareag.com

Copyright © 1997-2014 Software AG, Darmstadt, Germany.

SEARCH   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT