Table of Contents
Advertisement
Symantec® ServiceDesk Customization Guide 7.0
7.
Open the local machine settings on the primary application server by right clicking
the task tray application and selecting Settings. If the task tray app is not there, you
can launch it from the Workflow Designer -> Tools program group. Edit the server
marked as "(local)" and make sure the IP address is the actual server IP and NOT
the load balancer IP. The Deployment Root URL should also point to the local
machine. While in the Local Machine Info editor make sure that the "Do Not Process
Timeouts and Escalations" checkbox is checked.
Step4: Setting up Session Management
At this point, you can configure your load balancer for the entire cluster.
These steps will require you to have the ability to add exchanges in the Configuration
and Logging Tool, a feature that is normally not available. Our support staff has the
ability to temporarily expose this feature in your environment. You'll need to run these
steps on all of your application servers.
1.
Open windows explorer and browse to the Process Manager directory. By default it is
in Program Files\Altiris\Workflow Designer\Ensemble. Open the web.config file here.
Locate the DataAccessConfiguration section and find the ConnectionString node.
Copy the connection string out of the value attribute of this node so that it's in your
clipboard.
2.
Open the Configuration and Logging Tool and go to the Exchange Configuration tab.
Note on the left the currently selected Configuration. It should be LBQ_Server_Core.
Add a new exchange by clicking the Add button on the right. The type of the new
exchange should be SqlExchangeConfiguration. Give it the name
SharedPortalSessions. Paste the connection string from the web.config file into the
Connection String field. Save the exchange configuration.
3.
Find the exchange named LBME.ProcessManagerSessions and edit it. In the Deliver
to Queue dropdown find and select the SharedPortalSessions exchange that you just
created. Save the exchange. Then click Save on the main screen.
4.
Restart IIS.
5.
Perform steps 1 through 4 on the other servers.
66
Advertisement
Table of Contents
