Configuring the Object Broker Service
The Windchill Risk and Reliability Object Broker Service supports load balancing.
To configure the Object Broker Service:
1. Ensure your network architecture is valid.
a. Have a separate database server setup.
b. Have two machines ready to host two Object Broker Servers.
c. Have a machine ready to host Long Running Task Servers.
d. Have a machine ready to host the Web Server.
e. Have a load balancing gateway server prepared.
2. Install all the component of the Enterprise Edition to the first Object Broker Server.
3. Configure the first Object Broker Server:
a. Create a new Windchill Risk and Reliability database, convert an existing database, or copy a RelEnt.rlx file that points to an existing database to the installation folder.
 |
The connection between Windchill Risk and Reliability and its SQL Server or Oracle database only needs to be created on the initial server used to host the Object Broker Service. All other servers used to balance the Object Broker will refer to this connection, which exists as a file titled RelEnt.rlx.
|
b. Stop and disable the following services:
▪ Windchill Risk and Reliability Alert Service
▪ Windchill Risk and Reliability Long Running Task Service
c. Modify clients.config to point to the appropriate servers:
a. Modify the addresses for the following contracts to point to the load balancing gateway server:
▪ Relex.BusinessObjects.IService
▪ Relex.Windchill.IWindchillIntegrationServer
▪ Relex.Security.IAccessManager
▪ Relex.Security.IUserGroupManager
b. Modify the addresses for the following contracts to point to the machine that is hosting the Long Running Task Service:
▪ Relex.BusinessObjects.CalculationServer.ICalculationServer
▪ Relex.BusinessObjects.IEnterpriseUpsizeServer
▪ Relex.BusinessObjects.IMagicButtonServer
▪ Relex.Windchill.IWindchillIntegrationLRTServer
▪ Relex.Report.Common.IReportGenerator
▪ Relex.BusinessObjects.FileCreation.IFileCreationServer
▪ Relex.BusinessObjects.IAttachmentServer
▪ Relex.BusinessObjects.ICacheManager
▪ Relex.BusinessObjects.RecordNumbers.IRecordNumberManager
▪ Relex.AuditTrail.IAuditTrailServer
▪ Relex.BusinessObjects.LRTJobs.ILRTJobNotifier
▪ Relex.BusinessObjects.IServerTaskManager
▪ Relex.BusinessObjects.IServerTaskProgressManager
▪ Relex.BusinessObjects.ITaskManager
▪ Relex.BusinessObjects.ITaskManagerClient
▪ Relex.BusinessObjects.ICaftaImport
▪ Relex.License.ILicenseManager
d. Stop the first Object Broker Service. You will start it again later.
4. Install all the component of the Enterprise Edition to the second Object Broker Server.
5. Configure the second Object Broker Server:
a. Stop and disable the following services:
▪ Windchill Risk and Reliability Alert Service
▪ Windchill Risk and Reliability Long Running Task Service
b. Modify appsettings.config to point to RelEnt.rlx on the first Object Broker Server.
If the RelEnt.rlx file on the first Object Broker Server is not accessible from this second server, you can copy it from there to the second server.
c. Modify clients.config to point to the appropriate servers, referring to step 3.c.
d. Stop the Object Broker Service. You will start it again later.
6. Install all the component of the Enterprise Edition to the Long Running Task Server.
7. Configure the Long Running Task Server:
a. Modify appsettings.config to point to RelEnt.rlx on the first Object Broker Server.
If the RelEnt.rlx file on the first Object Broker Server is not accessible from the Long Running Task Server, you can copy it from there to this server.
b. Stop and disable the Object Broker Service.
c. Modify clients.config to point to the appropriate servers, referring to step 3.c.
d. Restart the following services:
▪ Windchill Risk and Reliability Alert Service
▪ Windchill Risk and Reliability Long Running Task Service
8. Start the Object Broker Service on both the first and second Object Broker Servers.
9. Configure the Web Server:
a. Modify appsettings.config to point to RelEnt.rlx on the first Object Broker Server.
If the RelEnt.rlx file on the first Object Broker Server is not accessible from the Web Server, you can copy it from there to this server.
b. Modify clients.config to point to the appropriate servers, referring to step 3.c.
10. Set up the load balancing gateway server to refer to both the first and second Object Broker Servers. As explained in Load Balancing Gateway, how you do this depends on the type of load balancer you are using.
11. If necessary, modify bindings.config:
|
|
The default settings in this configuration file are reasonable for most customers. However, you can modify them to support ‘best practice’ TCP load balancing for your particular setup.
|
a. For connectionPoolSettings, enter the values that meet your needs.
The default is 5000. This is the maximum number of outboard connections per endpoint. It is used to throttle the number of connections, both outbound from the client and inbound on the server.
The 5000 default value is arbitrarily large, representing a nearly infinite value. You can lower the maximum number of outboard connections per endpoint to a much smaller value if you want. For example, if you lower it to 100, only 100 connections can be made from all clients. This includes the possibility of having multiple connections from a single client machine. The 101st connection would attempt to connect for the number of seconds specified for leaseTimeout. If an open connection did not become available in this amount of time, the connection would be rejected.
b. For idleTimeout, indicate how long Windchill Risk and Reliability is to wait before closing an open connection that is idle.
The default is 30 seconds. This means that if you hit a load balancer and get directed to a particular backend machine, you stay connected to this machine for 30 seconds before reconnecting through the load balancer.
c. For leaseTimeout, indicate how long Windchill Risk and Reliability is to wait before reopening a current connection.
The default is 30 seconds. This is the amount of time that a client is to hold on to a connection that is not being used. For example, if you refresh the FRACAS Incidents table and then take no further action in this amount of time, the connection is then closed.
12. On user machines, install the client software from the first Object Broker Server.
|
|
Be sure that you navigate to this server and do not accidentally install the client software from the load balancing gateway server.
|
The Object Broker Service is now configured for load balancing.