Plug-in aliases scenarios
Following are scenarios of how aliases affect the behavior of the AR System server when it accesses plug-ins.
In this topic:
Vendor form accessing the ARDBC plug-in scenario
Server-Plugin-Alias: RMDY.ARDBC.XML RMDY.ARDBC.XML myhost
A vendor form that accesses the ARDBC plug-in named RMDY.ARDBC.XML is redirected to the plug-in by the same name on the plug-in server running on myhost.
Workflow accessing the ARF plug-in scenario
Server-Plugin-Alias: RMDY.ARF.PERL.myhost RMDY.ARF.PERL myhost
Workflow that accesses the ARF plug-in named RMDY.ARF.PERL.myhost is redirected to the RMDY.ARF.PERL plug-in on the plug-in server running on myhost.
Vendor form accessing the ARDBC plug-in scenario
Server-Plugin-Alias: RMDY.ARDBC.LDAP.fred RMDY.ARDBC.LDAP
myhost:11001
A vendor form that accesses the ARDBC plug-in named RMDY.ARDBC.LDAP.myhost.1 is redirected to the RMDY.ARDBC.LDAP plug-in on the plug-in server running on myhost and listening at port number 11001.
AR System server accessing the AREA plug-in scenario
Server-Plugin-Alias: AREA AREA myhost
When the AR System server accesses the AREA plug-in, it connects to the plug-in on the plug-in server that is running on myhost. Only one AREA plug-in can exist, so use the reserved name AREA for the alias.