Identifying the active state of Distributed Server Option
To verify whether Distributed Server Option ( DSO ) is active, perform the following steps:
- Query for pending DSO operations: From AR System Administration Console, select System > Distributed Server Option > Pending DSO Operations.
- Query to determine the number of items yet to be processed: Query for items with
CreateDate
before a specified date and time, and refresh the query results periodically to determine if the count is decreasing and at what rate. - Access the host system and verify the task list including the DSO server process name (for example, ardsoj81_build001.jar).
- Identify the Java DSO process using the server process name.
Identifying the Java DSO process
Perform the following steps to identify the Java DSO process using the server process name:
- Open AR System Management Console > AR System Server Group Console > Manage Process tab.
- From Process Name, select DSO process.
Setting DSO to active state
Perform the following steps if DSO is not active:
- Verify that there is a license for AR Distributed Server in
AR System
. Perform this step on both, the target and destination
AR System server
.
From AR System Administration Console, select System > General > Add or Remove Licenses - Verify that the
DSO
server process is included in the armonitor configuration file and is not commented.
- On Windows: Open armonitor.cfg and verify that the line with an entry for
ardsojversion_buildbuild number.jar
does not start with #. - On UNIX: Open armonitor.conf and verify that the line with an entry for
ardsojversion_buildbuild number.jar
does not start with #.
- On Windows: Open armonitor.cfg and verify that the line with an entry for
- Verify the DSO connection information from Centralized Configuration.
- Check for errors reported by the server process in the arerror.log file by searching for
Distrib
to identify messages related to DSO .
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.