Configure client connectivity

You can use the Client Connectivity section to select which protocol(s) a client needs to use to communicate with a Communication Driver on a per instance basis. The DDE/SL, OPC, and PCS protocols are selected by default when a Communication Driver is not running.

Configure Client Connectivity

1. In the OI Server Manager, navigate to the Configuration node.

   1. Expand the Operations Integration Server Manager node, expand the node group, and then expand Local.

   2. Expand the Communication Driver, and then select Configuration.

   The Global Parameters tab appears in the details pane.

2. In the Client Connectivity section, uncheck the protocol(s) that you wish to disable. A client cannot connect to the Communication Driver instance using the disabled protocol(s).

   Note: The PCS section is disabled if the PCS Plug-In is not installed. For more information on installing the PCS Plug-In, refer to PCS in the 'Supported Client Protocols' section.

3. For PCS IData clients, there is an option to modify the PCS Scope Name field to any scope name of your choice.

   The default PCS Scope Name is set to:

   OI

   lt;OIServerInstanceName>
   lt;ComputerName>

   • OI uniquely identifies the scope name as belonging to the OI Product line

   • $ is a separator in case the parts of the scope need to be parsed. The OIServerInstanceName and ComputerName must not contain $.

   • OIServerInstanceName is the instance of the Communication Driver as viewed in the OCMC.

   • ComputerName is the name of the machine on which the Communication Driver is running.

     Example of a default PCS Scope Name:

     

     If you are using the default PCS Scope Name, ensure that you save the configuration of the Communication Driver instance. This ensures that a remote node that connects to the Communication Driver instance sees the default configuration of the local node only.

     The scope name must be unique across all computer nodes in a Galaxy. The default scope name can be modified using the text field.

     Note: The scope name must not contain a colon :

     It is recommended to follow this syntax to ensure that the scope name of a Communication Driver instance is unique within a Galaxy, though not compulsory.The PCS Scope Name can be customized to any preferred name. For example, if the computer running the Communication Drivers is the only computer in a Galaxy, and you want to shorten the PCS Scope Name used in item names, then PCS Scope Names such as PLC1, PLC2, ABCIP1, ABCIP2, or SIDIR1 could be configured for the Communication Driver instance.

     Note: If a duplicate PCS Scope Name is defined in a Galaxy, then PCS clients may fail to connect to the Communication Driver with the duplicate name.

     You can restore default PCS scope name by selecting Default. Refer to "Access data using PCS" for more details on the default PCS scope name syntax.

4. Select Save.