Using the lbutil.exe tool to update connection strings

Article:HOWTO80684  |  Created: 2012-10-17  |  Updated: 2012-11-02  |  Article URL http://www.symantec.com/docs/HOWTO80684
Article Type
How To



If you need to update connection strings, you can use the lbutil.exe tool. In previous versions of Workflow you can update the Process Manager connection string in the web.config file. However, in version 7.5 and later the connection string is encrypted. To change the encrypted string you must either use the lbutil tool or reinstall Process Manager to change the string in the installation wizard.

 

Note: If you run Workflow in a large environment and have more than one Workflow Server set up in your cluster, be sure to run the lbutil command on each Workflow Server computer.

 

You can use the lbutil tool to perform any of the following actions. For instructions, see the Workflow 7.5 User Guide.

  • Change the Process Manager connection string. You can use lbutil.exe to change the Process Manager connection string. This function of lbutil is useful when you change a password in a connection string or move the database to a new server. Because the Process Manager connection string is encrypted, the only way to update the string is to use lbutil or the Workflow Installer.
  • Change Workflow persistence. Workflow Persistence refers to how "state" data is stored; for example, when a workflow is running and stops at a dialog workflow component to gather user input. The current state of that workflow is stored in either the database or the file system. You can change Workflow Persistence from File SymQ to SQL SymQ and from SQL SymQ to File SymQ. You can also change the connection string of an existing SQL SymQ. This function of lbutil is useful when you change a password in a connection string or move the database to a new server. However, you can also make this change in the UI using Workflow Explorer SymQ configuration.
  • Set the ORM connection string. This function of lbutil is useful when you change a password in a connection string or move the database to a new server. However, you can also make this change in the UI using Workflow Explorer SymQ configuration.
  • Chain commands. You can chain multiple lbutil commands together; for example, if your implementation of Workflow includes SQL authentication for database access and you need to change the password. If you change the SQL password in this instance, you must also change the connection strings for Process Manager, SQL Persistence, and ORM. Instead of making multiple changes, you can use one lbutil command and include the command to restart the Workflow service.

 

To change the Process Manager connection string

  1. On the Workflow Server where you are logged in as Admin, open a command window.
  2. Pass the following flags into lbutil:
    • -updatepmconnection
    • -connectionstring [Use the database connection string.]
    • -webconfig [Use the path of Process Manager web.config. This line is optional and should be left blank for normal usage.]
  3. Restart the Symantec Workflow service for the changes to take effect.

Refer to the following example of how to change the Process Manager connection string:

lbutil.exe -updatepmconnection

-connectionstring "Data Source=(local);Initial

Catalog=ProcessManager;User Id=user;Password=pwd;"

 

To change Workflow persistence

  1. On the Workflow Server where you are logged in as Admin, open a command window.
  2. Pass the following flags into lbutil:
    • -setworkflowpersistence
    • -persistencetype [SQL or file]
    • -connectionstring [If SQL, then enter the database connection string. If File, then enter the folder where the utility should store the files.]
  3. Restart the Symantec Workflow service for the changes to take effect.

Refer to the following example of how to change Workflow Persistence with SQL SymQ:

lbutil.exe -setworkflowpersistence

-connectionstring "Data Source=(local);Initial

Catalog=ProcessManager;User Id=user;Password=pwd;"

 

To set the ORM connection string

  1. On the Workflow Server where you are logged in as Admin, open a command window.
  2. Pass the following flags into lbutil:
    • -setormconnection
    • -connectionstring [Use the database connection string.]
  3. Restart the Symantec Workflow service for the changes to take effect.

Refer to the following example of how to set the ORM connection string:

lbutil.exe -setormconnection

-connectionstring "Data Source=(local);Initial

Catalog=ProcessManager;User Id=user;Password=pwd;"

 

To chain lbutil.exe commands

  1. On the Workflow Server where you are logged in as Admin, open a command window and pass in the commands that you want to chain.

Refer to this example:

lbutil.exe -updatepmconnection -setormconnection -setworkflowpersistence -persistencetype SQL -connectionstring "Data Source=(local); Initial Catalog=ProcessManager;User Id=user;Password=pwd;" NET STOP SWFSVR NET START SWFSVR

If you omit the commands to stop and start the Symantec Workflow service, you must restart the service manually for the changes to take effect.

 



Article URL http://www.symantec.com/docs/HOWTO80684


Terms of use for this information are found in Legal Notices