Copyright © Cloud Software Group, Inc. All rights reserved. |
To run the TIBCO iProcess Objects Server on multiple machines, it must be installed on each of the machines in the cluster on which it will be running. As an example, if the TIBCO iProcess Objects Server is installed on two machines in the cluster, the process_config table will appear as follows:
Multiple instances of the TIBCO iProcess Objects Server can be run on a single machine, resulting in all TIBCO iProcess Objects Servers running from the same $SWDIR directory and using the same database. This allows you to run multiple TIBCO iProcess Objects Servers without requiring you to have a cluster. The reasons for running multiple instances of TIBCO iProcess Objects Server on the same machine are:When the TIBCO iProcess Objects Server is initially installed on a machine, it becomes instance 1 by default. A new installation of a TIBCO iProcess Objects Server on a machine will cause an entry for that server to be automatically added to the process_config table, as follows:
Once the initial installation is completed, additional instances of the TIBCO iProcess Objects Server can then be added to or deleted from the process_config table using the following swadm commands:For example, after adding a second instance to machine 1, the process_config table appears as follows:
For additional information about using the swadm utility, see iProcess Engine Administrator’s Guide.For information about configuring TCP ports for multiple instances, see the TCPServiceName parameters on This identifies the port number on which the TIBCO iProcess Objects Server will listen for client connections. This can be specified in the following ways:; for information about configuring UDP ports for multiple instances, see the UDPServiceName parameter on UDPServiceName.The Process Sentinels control the starting and stopping of multiple TIBCO iProcess Objects Servers that have been added to the process_config table.By default, once the Process Sentinels have started, they automatically start the processes in the process_config table. You can force all processes in the process_config table to be started or stopped by using the following commands:SWDIR\bin\swstartSWDIR\bin\swstop
• The UNIX TIBCO iProcess Objects Server includes a configuration file that specifies the values assigned to each TIBCO iProcess Objects Server configuration parameter. You can define a configuration parameter for each instance of the TIBCO iProcess Objects Server by appending the instance number to the parameter name (e.g., LogFileMaxSize03). For more information, see Configuring Multiple Instance Parameters on UNIX Systems.
• The Windows TIBCO iProcess Objects Server includes a configuration utility for administering configuration parameters. The configuration utility allows specification of parameters for each instance of the TIBCO iProcess Objects Server running on that machine. For more information, see Configuring Multiple Instance Parameters on Windows Systems.Specifying TCP and UDP ports for multiple instances of the TIBCO iProcess Objects Server works a little differently than the other configuration parameters. See TCPServiceName and UDPServiceName for more information.If you are using a TIBCO iProcess Objects Server that is multiple-instance capable, the name of the TIBCO iProcess Objects Server log, archive log, and audit log will include the instance number (XX) of the TIBCO iProcess Objects Server instance. The timestamp variable in the log file names:
• TIBCO iProcess Objects Server log files: the error occurs at a different date than the date the last error is logged. In the mean time, the previous log file will be archived as SWEntObjSvXX_timestamp.log, where the timestamp variable is the date when that log is generated.See Name and Location of the TIBCO iProcess Objects Server Log for more information.
TIBCO iProcess Objects Server archive log2
This file is the archived SWEntObjSvXX.log, where the timestamp variable is the date when the log is generated.
• Directed UDP Message - The AddNodeEx method is used to send a directed UDP message to a specific instance of the TIBCO iProcess Objects Server. This method contains an InstanceNumber parameter to specify the instance.
• Manually Create an SWNodeInfo Object- The MakeNodeInfoEx method is used to create an SWNodeInfo object for a specific instance of the TIBCO iProcess Objects Server. This method contains an InstanceNumber parameter to specify the instance.For more information about these methods of accessing multiple instances of the TIBCO iProcess Objects Server, see TIBCO iProcess Objects Programmer’s Guide.
• UDP Broadcast - Calling the getNodes method on sNodeManager causes a UDP broadcast to be issued on the LAN segment. The getNodes method returns an array of vNode objects, one for each TIBCO iProcess Objects Server that responded to the UDP broadcast. You can then call the getInstance method on the vNode object to determine the instance number of that TIBCO iProcess Objects Server.
• Directed UDP Message - Calling the verifyNode method on sNodeManager causes a directed UDP message to be sent to a specific instance of the TIBCO iProcess Objects Server. This method provides an aInstance parameter to specify the specific instance of the TIBCO iProcess Objects Server to receive the UDP message.
• Manually Create a vNodeId Object- You can construct a vNodeId object that represents the specific instance of the desired TIBCO iProcess Objects Server. Note that the constructor for the vNodeId object does not have an Instance parameter — you must use the aTCPPort parameter to uniquely identify the instance of the TIBCO iProcess Objects Server the vNodeId object is to represent.For more information about these methods of accessing multiple instances of the TIBCO iProcess Objects Server, see TIBCO iProcess Server Objects Programmer’s Guide.
Copyright © Cloud Software Group, Inc. All rights reserved. |