Tech Note 128 Configuring InBatch For Standalone PCs With SQL Server and IndustrialSQL Server

Transcription

1 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#: C reated: 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 1. Run the Microsoft SQL Enterprise Manager from the Microsoft SQL Server 6.5 folder and right-mouse click the SQL 6.5 icon as shown below: 1/13

2 2. Select Register Server from the dropdown menu as shown above. The Register Server dialog box will appear: 3. Type in the node name of the local computer in the Server listbox. (If you do not know the node name, you can find out by selecting Network from the Control Panel.) Select Use Trusted Connection. 4. Click the Modify button to complete the registration. (If this is a new server, you will see a Register button in place of the Modify button, of which you should click instead.) 5. Register one more server by entering the name LOCAL in the Server listbox. Again, select Use Trusted Connection. Click the Register button to complete the registration. 6. Complete the configuration of InBatch History as described in Chapter 3 of the FactorySuite System Administrator s Guide. You will need to complete all six steps 2/13

3 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 Logins dialog box will appear: 3/13

4 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. 4. Go back to the Microsoft SQL Enterprise Manager window and expand the Databases folder, then the IBHistory database icon, then the Group/Users folder as shown below: 4/13

5 5. Right- mouse click the IBAdmin group as shown above and select New User. The Manage Users dialog box will appear: 6. Enter the same user name in the User Name listbox that was entered in step 3. Select the correct Login and Group from the dropdown lists and click the Add button, then click the Close button to exit. The User Name should appear in the Microsoft SQL Enterprise 5/13

6 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. C onfigure the SQL C lient C onfiguration Utility 1. Start up the Microsoft SQL Server Client Configuration utility from the Microsoft SQL Server 6.5 folder. The SQL Server Client Configuration Utility window will appear: 6/13

7 2. Click the Net Library tab as shown above and verify that Named Pipes is selected for the Default Network. 3. Click the Advanced tab and verify that three entries are displayed in the Current Entries list: one that says "<local node name>_bd", another that says "LOCAL" and a third that says "InSQL." An example is shown here: 7/13

8 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. C onfigure the Mic rosoft OD BC D atabase Administrator 1. Open the Control Panel window and double- click the ODBC program icon. The ODBC Data Source Administrator dialog box will appear: 8/13

9 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. 6. Here are the example entries for the InBatch History MDB data source: 9/13

10 7. Here are the example entries for the InBatch History Server data source: 10/13

11 8. Here are the example entries for the InSQL data source: 9. And here are the example entries for the LocalServer data source: 11/13

12 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 History Administration dialog box will appear: Enter the same User Name and Password that was created in step 3 under the section "Configure the Security for SQL Server." The Domain should be the node name of the local computer. Click the OK button when finished. Note For more information on the InBatch History Administration utility, see the Wonderware InBatch User s Guide, which is available on the FactorySuite CD- ROM that includes the InBatch component. 12/13

13 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 C orporation, 100 Technology Drive, Irvine C A There is also technical information on our software products at Wonderware Technical Support, our WonderFax fax-ondemand system at (949) , and the C omprehensive Support Knowledge Base. For technical support questions, send an to [email protected]. back to top 2013 Wonderware C orporation. All rights reserved. Terms of Use. 13/13