OpenTP1 Version 7 Operation
![[Contents]](FIGURE/CONTENT.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
- On the RAP-processing server
Use the rapsetup command to set up the execution environment of the remote API facility.
- On the RAP-processing client
When using the RAP-processing client manager function, also execute the rapsetup command on the RAP-processing client to set up the execution environment of the remote API facility.
- On the RAP-processing server
Create the RAP-processing listener service definition.
- On the RAP-processing client
Create the user service definition and the user service network definition. In the user service network definition, include the dcsvgdef definition command with the -w option specified to indicate that communication is to take place via the remote API facility.
- Example definition:
- dcsvgdef -g service-group-name -h host-name -p port-number -w
If you are using the RAP-processing client manager facility, also create the RAP-processing client manager service definition.
For details about the definitions, see the manual OpenTP1 System Definition.
- On the RAP-processing server
Execute the rapdfgen command, specifying the RAP-processing listener service definition you created in (2) above as the input file. This creates the RAP-processing listener user service definition and the RAP-processing server user service definition.
The command outputs generated definitions to be under the $DCCONFPATH directory.
- Example of command execution:
- > rapdfgen RAP-processing-listener-service-definition-file-name
- On the RAP-processing client
If you are using the RAP-processing client manager facility, execute the rapdfgen command specifying the RAP-processing client manager service definition you created in (2) above as the input file. This creates the RAP-processing client manager user service definition under the $DCCONFPATH directory.
- Example of command execution:
- > rapdfgen -m RAP-processing-client-manager-service-definition-file-name
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.