Setting the Number of Starting Method Servers
When initializing an empty database, only one method server should be running to avoid update conflicts between multiple servers. The server monitor process that creates data on demand can cause a racing condition when multiple instances of the service managers start at the same time while running against an empty database. Therefore, prior to loading the database with base data, you must set the number of starting method servers to only one. Thereafter, you can optionally reset the number of starting method servers and load the remainder of your data.
 |
For more information on multiple method servers and background method servers, see Advanced Deployment Considerations.
|
To Verify the Number of Method Servers
In a typical use-case scenario only one Windchill Method Server will be running at this time. However, in certain cases, such as if the Windchill Configuration Assistant (WCA) was run before loading data, multiple method servers may be running. Attempting to continue in this scenario could result in corrupted data. Therefore it is recommended that you verify the number of method servers that are running before continuing.
1. Verify that the wt.manager.monitor.services property specifies only the method server and document all other services that are displayed for the property.
You must also disable any customized monitor service properties you may have defined. Execute the following command from the windchill shell to display the value assigned to wt.manager.monitor.services (perform this for your customized monitor services properties as well):
xconfmanager -d wt.manager.monitor.services
2. If only the method server is displayed, then only one method server is being used and no other steps are required. Otherwise, change the wt.manager.monitor.services to specify only the method server as follows:
xconfmanager -s wt.manager.monitor.services=MethodServer
-t <Windchill>/codebase/wt.properties -p
-t <Windchill>/codebase/wt.properties -p
3. Verify that the wt.manager.monitor.start.Method Server property exists, and if it does, verify that the value is set to 1.
If these conditions are true, then no other steps are required. Otherwise, set the value of the property to 1, if the property exists. Use the xconfmanager to apply these changes. Perform the following instructions from the windchill shell:
◦ To display the property value:
xconfmanager -d wt.manager.monitor.start.MethodServer
◦ To change the property value to a value of 1:
xconfmanager -s wt.manager.monitor.start.MethodServer=1
-t <Windchill>/codebase/wt.properties -p
-t <Windchill>/codebase/wt.properties -p
Now that only the method server is specified (limited to one), you can load the database. After the database is loaded, restore these properties to their original settings.