To add a resource adapter in cluster operation, open the context menu for the Resource Adapter node in the navigation tree's cluster subtree and choose Add Resource Adapter... Alternatively, you can click the required node and then run the Add command in the resource adapter list.
Enter the parameters for the resource adapter in the two tabs General and Common Properties. The parameters specified in Common Properties are the same for all the resource adapters in a cluster. Any change to these properties therefore affects all the resource adapters defined in the cluster, whereas the parameters specified in General are specific to each resource adapter:
Figure 27: Adding a resource adapter in cluster operation
Host (General)
Name or IPv4 address of the computer running the application server on which the resource adapter is deployed. The host specified here must match the value of <host> in a <host:port> entry of the resourceAdapterAddresses property of the deployment descriptor ra.xml for the resource adapter.
Listener Port (General)
Number of the listener port of the resource adapter for inbound communication. The host specified in Host and the listener port must match a <host:port> entry in the resourceAdapterAddresses property of the deployment descriptor ra.xml for the resource adapter. If no port is specified there, the specification must match the value in the inboundListenerPort property.
Within a cluster, the Management Console does not permit a value of 0 or no value to be entered. A port between 1025 and 65535 must be specified even if no inbound communication is planned.
MC-CmdHandler of the Resource Adapter (General)
These fields allow you to define an MC-CmdHandler that is available on the resource adapter computer and that can be adapted via the Management Console using the resource adapter's deployment descriptor ra.xml.
Click the ... button in Select MC-CmdHandler to display an additional dialog box in which you can enter the data for the MC-CmdHandler (listener port, password):
If the BeanConnect-RAR archive is also located on this computer, then you can use this MC-CmdHandler to edit the entries in the resource adapter's deployment descriptor
ra.xmlor update these entries in line with the entered parameters. You can do this using the commands Edit ra.xml of BeanConnect Resource Adapter RAR or Update ra.xml of BeanConnect Resource Adapter RAR in the resource adapter's context menu, see Resource adapter configuration file .
You can also use this MC-CmdHandler to modify the Log4j diagnostic settings.You can enter the fully qualified path name of the Log4j configuration file in Log4j Configuration File Path (optional).
The Log4j configuration file is always located on the computer on which the application server runs. This does not have to be the computer on which the BeanConnect resource adapter is located since the resource adapter cannot be uploaded to the application server computer before deployment.
If you want to change the resource adapter's logging configuration then an MC-CmdHandler must be running on the computer on which the application server runs.
Transaction Logging (Common Properties)
Specifies whether persistent transaction logs are written in the resource adapter in the case of outbound communication (FILE) or not (NONE). This property corresponds to the transactionLogging property in the resource adapter's deployment descriptor ra.xml. If transaction logging is configured then the resource adapter writes a separate log file for each transaction. The file name consists of the prefix tx. and a number.
Transaction Logging Directory (Common Properties)
Directory in which transaction logging is stored in the resource adapter. This property corresponds to the transactionLogDir property in the resource adapter's deployment descriptor ra.xml.
Proxy Reconnect Count (Common Properties)
Specifies the number of connection requests (calls to getConnection()) after which the assignment between the resource adapter instance and the proxy application must be made again. This property controls the usage-driven reassignment of a resource adapter instance to a proxy application. It corresponds to the proxyReconnectCount property in the resource adapter's deployment descriptor ra.xml.
The default value is 100.
If a cluster is operated with more resource adapter instances than proxy instances then a larger value or the value 0 should be entered for this parameter. The value 0 deactivates the reconnect counter.
Proxy Reconnect Interval (min) (Common Properties)
Specifies the time in minutes after which the assignment between the resource adapter instance and the proxy application must be made again. This property controls the timedriven reassignment of a resource adapter instance to a proxy application. It corresponds to the proxyReconnectInterval property of the resource adapter's deployment descriptor ra.xml.
The default value is 10 minutes.
If a cluster is operated with more resource adapter instances than proxy instances then a larger value or the value 0 should be entered for this parameter. The value 0 deactivates the reconnect timer.