Remedy - Server - How to configure multiple ARDBC LDAP vendor forms against multiple domains

Knowledge Article

Remedy - Server - How to configure multiple ARDBC LDAP vendor forms against multiple domains
How to configure multiple ARDBC LDAP vendor forms against multiple domains
Remedy AR System Server
AR System
Remedy AR System v.9.1.x
Remedy AR System Server
AR System
Remedy AR System v.9.1.x
How can I create multiple ARDBC LDAP vendor forms against multiple domains in 9.1.x?
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.

Related information:
Configuring the ARDBC LDAP plug-in - BMC Documentation
Remedy - Server - [ ARS v.8.1.x ] How to configure ARDBC LDAP for multiple vendor forms for each of domains
Remedy - Server - [ ARS v.9.0.x ] How to setup Multiple ARDBC LDAP for Multiple Vendor forms in Windows
https://docs.bmc.com/docs/display/ars2002/Configuring+the+ARDBC+LDAP+plug-in

Setting up Multiple ARDBC LDAP Plugins
The following steps will guide you through setting up secondary ARDBC LDAP plugin server(s) on a version 9.1 (>=9.1.02)  through 18.08 AR System where a primary plugin server is already configured and working.
For versions 19.02 and above, please refer to the "Configuring the ARDBC LDAP plug-in - BMC Documentation"  section in the on-line documentation.
This document assumes that an existing AR System server and Plugin server are already successfully configured and running with ARDBC LDAP.
These steps are written for Windows but the same methodology would apply to Unix as well.  A new ARDBCLDAP Plugin Server can be created for each additional domain or forest that you need to access with a vendor form. 

1- Create a new directory for each additional ARDBCLDAP Plugin Server under:  ..\ARSystem\pluginsvr  directory:
                C:\Program Files\BMC Software\ARSystem\pluginsvr\ARDBCLDAP1
                C:\Program Files\BMC Software\ARSystem\pluginsvr\ARDBCLDAP2

2- Copy log4j_pluginsvr.xml and pluginsvr_config.xml from: ..ARSystem\pluginsvr   into each of the new folders you created.

3- Edit the pluginsvr_config.xml for each new ARDBCLDAP Plugin Server
         a- Change the port to valid, unused port.
         b- Change the value of the PluginSvrName to note the new plugin name and port.
         c- Set the logging level to DEBUG until it is working properly.
         d- change the value of pluginSvrAlwaysOnLogName to denote the new port #
         e- Remove all the plugins between the <plugins>  and </plugins> tags except for ARDBC.LDAP

              For example:
<pluginsvr_config>
      <port>9910</port>
      <regPortMapper>false</regPortMapper>
      <encryptionPolicy>2</encryptionPolicy>
      <publicKeyAlg>4</publicKeyAlg>
      <publicKeyExpiry>86400</publicKeyExpiry>
      <dataEncryptionAlg>1</dataEncryptionAlg>
      <dataKeyExpiry>2700</dataKeyExpiry>
      <numCoreThreads>5</numCoreThreads>
      <numSelectorThreads>2</numSelectorThreads>
      <workQueueMonitorLogInterval>0</workQueueMonitorLogInterval>
      <workQueueTaskThreshold>5</workQueueTaskThreshold>
      <reloadDelay>30000</reloadDelay>
      <enableNativeBridge>false</enableNativeBridge>
      <maxThreads>10</maxThreads>
      <excessCoreThreadsIdleKeepAliveTimeInSecond>0</excessCoreThreadsIdleKeepAliveTimeInSecond>
      <supportNativePluginHost>false</supportNativePluginHost>
      <loadNativePluginHost>false</loadNativePluginHost>
      <pluginSvrLogEnable>True</pluginSvrLogEnable>
      <pluginSvrLogFile>C:/Program Files/BMC Software/ARSystem/ARServer/Db/arjavaplugin.log</pluginSvrLogFile>
      <pluginSvrName>PluginServer_ARDBCLDAP1_9910_IDGAA5V0GEM72APGXTRQPGBG3KPU43</pluginSvrName>
      <pluginSvrLogLevel>DEBUG</pluginSvrLogLevel>
      <pluginSvrLogMaxFileSize>5242880</pluginSvrLogMaxFileSize>
      <pluginSvrLogMaxHistory>10</pluginSvrLogMaxHistory>
      <pluginSvrAlwaysOnLogName>C:\\Program Files\\BMC Software\\ARSystem\\ARServer\\Db\\pluginsvr_{AR_Server_Name}_9910_alwayson.log</pluginSvrAlwaysOnLogName>
      <pluginSvrAlwaysOnCopies>20</pluginSvrAlwaysOnCopies>
      <pluginSvrAlwaysOnBufferSize>0</pluginSvrAlwaysOnBufferSize>
<plugins>
<plugin>
      <name>ARSYS.ARDBC.LDAP</name>
      <classname>com.bmc.arsys.plugins.ardbcldap.ARDBCLDAPPlugin</classname>
      <filename>C:\Program Files\BMC Software\ARSystem\pluginsvr\ardbcldapplugin91_build003.jar</filename>
      <pathelement type="path">FRESH</pathelement>
      <pathelement type="location">C:\Program Files\BMC Software\ARSystem\pluginsvr\ardbcldapplugin91_build003.jar</pathelement>
</plugin>
</plugins>
</pluginsvr_config>

4- Edit the log4j_pluginsvr.xml for each new ARDBCLDAP Plugin Server.
     Change the log filename to indicate which Plugin Server this is.
     For Example:
                   <param name="File"
                   value="C:/Program Files/BMC Software/ARSystem/ARServer/Db/arjavapluginARDBCLDAP1.log"/>

5- Create a 'conf' directory within each new directory you created.
     For example:
                   C:\Program Files\BMC Software\ARSystem\pluginsvr\ARDBCLDAP1\conf
                   C:\Program Files\BMC Software\ARSystem\pluginsvr\ARDBCLDAP2\conf

6- Edit the armonitor.cfg file:

         a- Duplicate the line for the main Java Plugin Server once for each new ARDBCLDAP Plugin Server
         b- The line will contain a -classpath value that points to the ..\ARSystem\pluginsvr directory.
                     “java" -Xmx512m -classpath "C:\Program Files\BMC Software\ARSystem\pluginsvr; "....
         c- Edit the first classpath to point to the new directory you created within ..\ARSystem\pluginsvr
         d- Edit the -i parameter so that it points to the new directory you created within ..\ARSystem\pluginsvr

              For example:
                           "%BMC_JAVA_HOME%\java" -Xmx1024m -classpath "C:\Program Files\BMC Software\ARSystem\pluginsvr\ardbcldap1;C:\Program Files\BMC Software\ARSystem\pluginsvr\arpluginsvr91_build003.jar;
                           C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arcmnapp91_build003.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR_Server_Name}
                            -i "C:\Program Files\BMC Software\ARSystem\pluginsvr\ardbcldap1" -m

                           "%BMC_JAVA_HOME%\java" -Xmx1024m -classpath "C:\Program Files\BMC Software\ARSystem\pluginsvr\ardbcldap2;C:\Program Files\BMC Software\ARSystem\pluginsvr\arpluginsvr91_build003.jar;
                           C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arcmnapp91_build003.jar" com.bmc.arsys.pluginsvr.ARPluginServerMain -x {AR_Server_Name}
                           -i "C:\Program Files\BMC Software\ARSystem\pluginsvr\ardbcldap2" -m
 

7- Edit the ar.cfg file:
     Add a Server-Plugin-Alias for each new plugin server.
         a- Provide the unique port that was added to the pluginsvr_config.xml.
         b- Change the first parameter to be a unique name for the Plugin Server

              For example:
                            Server-Plugin-Alias: ARSYS.ARDBC.LDAP1 ARSYS.ARDBC.LDAP remedyprod:9910
                            Server-Plugin-Alias: ARSYS.ARDBC.LDAP2 ARSYS.ARDBC.LDAP remedyprod:9911

              Note: Normally you would add this through the Centralized Configuration UI.  We did it from the file directly since when we added it through the UI, the parameter seemed to disappear. You should be able to do it either way.

8- Use the ARDBC LDAP Configuration form to create the settings​
         a- Configure for one domain.
              We will copy these settings later into the new configurations.

 9- Copy the primary ar.cfg into a new ar.cfg file in the 'conf' of new ARDBCLDAP Plugin Server, e.g.  C:\Program Files\BMC Software\ARSystem\pluginsvr\ARDBCLDAP1\conf

         a- Delete all other settings except following:
                       Server-Name:
                       Configuration-Name:
                       TCD-Specific-Port:
                       Server-Connect-Name: 
                       Remedy-App-Service-Password:

         b- Change the configuration name to some unique value e.g. ARDBCLDAP1
              The snippet of ar.cfg should look like as below.
                       Server-Name: {AR_Server_Name or Load Balancer if being a server group}
                       Configuration-Name: ARDBCLDAP1
                       TCD-Specific-Port: {specific available port}
                       Server-Connect-Name: {AR_Server_FQDN}
                       Remedy-App-Service-Password: PlfkrqkgYmWrHle1DZOoXErq9…

10- Open the AR System Configuration Component form.

         a- Create a new entry with the Configuration-Name: configured in step 8d
         b- Provide a ‘Type’ of  com.bmc.arsys.ldap.ardbc
         c- The entry should look as below:

               User-added image


11- Review the existing ARDBC LDAP Settings.

         a- Go to AR System Administration Console > General > Centralized Configuration.
         b- Select the original settings so you can use to manually configure the new plugin.

               User-added image


12- Configure the LDAP settings for new pluginserver instance using Centralized Configuration UI

         a- Go to AR System Administration Console > General > Centralized Configuration
         b- Select the component name which was created in step 9.

               User-added image


13- Add the LDAP server settings for the new Plugin using the information from step 10.

         a- Click on the ‘Add’ button to add each new ‘Setting Name’ and ‘Setting Value’.
         b- Click ‘Apply’ after adding each one.
         c- The settings should look as below:

               User-added image
 

14- Repeat steps 8-14 for each additional ARDBC LDAP Plugin server.

15- Restart AR System.
       This is needed to launch the new Plugin Servers and for arserver to read the new Server-Plugin-Alias  parameters.

       Create a new vendor form using the new ARDBCLDAP Plugin Servers.
       The ‘New Vendor’ form Wizard should display a new 'Vendor' item for each of the new ARDBCLDAP Plugin Servers:

               User-added image
 
Remedy AR System Server
AR System
Remedy AR System v.9.1.x
Attachment(s):