Tech Note 128
Configuring InBatch For Standalone PCs With SQL Server and
IndustrialSQL Server
All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the
Terms of Use for more information. Topic#: 000763
Created: November 6, 1998
This Tech Note shows how to set up Wonderware® InBatch™, IndustrialSQL™ Server and Microsoft® SQL Server to run on a standalone computer. The resulting configuration will allow InBatch to log data to a SQL Server database, as well as allow you to use the InBatch reporting tools to view pre-formatted reports on various batch details that are read from the SQL Server database.
Note This Tech Note can also be used when installing InBatch, IndustrialSQL Server and Microsoft SQL Server on more than one node to log InBatch History Data.
Procedure
Install IndustrialSQL Server and InBatch
Install IndustrialSQL Server by following the instructions in the Wonderware FactorySuite
System Administrator’s Guide, Chapter 3 Installation, which is available on the FactorySuite CD-ROM. When prompted to select the optional components to install for IndustrialSQL Server, select the InSQL AutoStart option.
Then, install InBatch by continuing to follow the instructions in the Wonderware FactorySuite System Administrator’s Guide, Chapter 3 Installation.
Note You must install IndustrialSQL Server first before installing InBatch and configuring InBatch History.
Register the Servers on Microsoft SQL Server
described in the manual. (Note that the procedure assumes the Server name is called "Zeus." Substitute the name entered in step 2 above for Zeus in the Administrator’s Guide.)
Configure Microsoft SQL Server
This section describes how to configure the various features of Microsoft SQL Server so they will work with InBatch and IndustrialSQL Server.
Configure the Security for SQL Serv er
1. Start up Microsoft SQL Enterprise Manager and click on the SQL Server icon that has the same node name as your computer as shown below (example: ANDREW300). It’s the one with the traffic light icon.
2. Right-mouse click the Logins folder as shown above and select New Login. The Manage
3. Enter in the Login Name listbox the name of the person that will be accessing the SQL Server database from InBatch. Enter the password for that user in the Password listbox and keep the default for the Default Language, if desired. Click the Add button when finish.
5. Right-mouse click the IBAdmin group as shown above and select New User. The Manage
Users dialog box will appear:
Manager window under the IBAdmin group icon as shown here:
7. Go back to the Microsoft SQL Enterprise Manager window and expand the IBArchive database icon, then the Groups/Users folder. Right-mouse click the IBAdmin group as shown in step 4 and select New User.
8. Add the same User Name to the IBAdmin group under the IBArchive database by repeating step 5.
Configure the SQL Client Configuration Utility
2. Click the Net Library tab as shown above and verify that Named Pipes is selected for the Default Network.
4. If any of the three entries in the Current Entries list do not exist, then you will need to add them by entering the appropriate values in the Server, DLL Name and Connection String listboxes and clicking the Add/Modify button. Below are some example entries. Note that the values you enter may vary from what is listed in the examples below.
Configure the Microsoft ODBC Database Administrator
1. Open the Control Panel window and double-click the ODBC program icon. The ODBC Data
2. Click the System DSN tab as shown above.
3. Verify that the following four data sources exist in the System Data Sources list: InBatch History MDB, InBatch History Server, InSQL and LocalServer. (Note that the names for these four data sources are case sensitive.)
4. Click the Add button to add any missing data source names. Below are some example entries. Note that the values you enter may vary from what is listed below. When finished, click the Apply button, then the OK button. (If you don’t need to add any missing data sources, then click the OK button.)
5. The InBatch History MDB entry provides access to the Microsoft Access database, which is a backup to Microsoft SQL Server in case the connection to the SQL server is lost. This is useful only if the InBatch History Database (that is Microsoft SQL Server) is located on a different computer. We recommend that you go ahead and configure the DSN for
InBatch History MDB anyway.
8. Here are the example entries for the InSQL data source:
Running the InBatch History Administration Utility
The InBatch History Administration utility is used to record the user that will use the Batch Manager to log onto Microsoft SQL Server. Start up the InBatch History Administration utility by selecting the History Administration application from the InBatch Server program folder. The
Testing InBatch With SQL Server and IndustrialSQL Server
Microsoft SQL Server, the ODBC Data Source and IndustrialSQL Server should all now be
configured to run with InBatch data logging. Follow these steps to ensure that the InBatch data is being logged correctly in Microsoft SQL Server:
1. Copy the demonstration configuration file, InBatch\cfg\ibDemoDB, to the directory InBatch\cfg\config_A and start up the InBatch Environmental Display.
2. Select Start InBatch Runtime Services from the InBatch menu. There should be no errors in the logger on failing to connect to Microsoft SQL Server. Also, you should see the Batch Manager service transitioning to the running state.
3. Schedule a batch through BatchSched and run the batch to completion through BatchDspl.
4. Clean up the schedule through BatchSched and start the ReportDispl.
5. Select Open from the File menu and select B_MatlInputs.rpt. You should see a dialog box prompting you for the Campaign ID. Keep the default "*" value and click the OK button.
6. You should see a report that displays all the manual inputs to the demonstration recipe. This report proves that Microsoft SQL Server is working properly with InBatch. If the report is missing, verify the steps shown in this Tech Note or contact your local Wonderware distributor or Wonderware Technical Support.
A. Brodie and R. Ekstein
The Tech Note is published occasionally by Wonderware Technical Support. Editors: Sabrina Abercromby and Kelly Hauser; Publisher: Wonderware Corporation, 100 Technology Drive, Irvine CA 92618. There is also technical information on our software products at Wonderware Technical Support, our WonderFax fax-on-demand system at (949) 450-5050, and the Comprehensive Support Knowledge Base.
For technical support questions, send an e-mail to [email protected].
back to top