Setup BNIP for Network operation

C. Logan 9/12/01

This procedure assumes that BNIP is running on a network cluster consisting of two BNIP client machines and one Ballot Now server machine.

1.  Install Ballot Now on BNIP client machine using Ballot Now Setup.exe

2.  Using ODBC Data Source Administrator in Control Panel, change ODBC on BNIP client as follows:

a.  Select BallotNow Local under System DSN tab.  Press Configure...
b.  Verify Data source name is BallotNow Local under ODBC tab
c.  On Login tab, verify User ID & password is "dba" "resolve", and make sure "Encrypt password" is checked.
d.  On Database tab, verify Server Name is BNLocalServer.  Make sure all other fields are blank.
e.  On Network tab, check box "TCP/IP".  Verify "Shared memory" is checked.
f.  Click "OK"

a.  Select BallotNow Security under System DSN tab.  Press Configure...
b.  Verify Data source name is BallotNow Security under ODBC tab
c.  On Login tab, verify User ID & password is "dba" "resolve", and make sure "Encrypt password" is checked.
d.  On Database tab, verify Server Name is BNSecurityServer.  Make sure all other fields are blank.
e.  On Network tab, check box "TCP/IP".  Verify "Shared memory" is checked.
f.  Click "OK"

3.  Using ODBC Data Source Administrator in Control Panel, change ODBC on Ballot Now Server as follows:

a.  Select BallotNow Local under System DSN tab.  Press Configure...
b.  Verify Data source name is BallotNow Local under ODBC tab
c.  On Login tab, verify User ID is "dba" & password is blank.
d.  On Database tab, verify Server Name is BNLocalServer.  Start line should be modified to launch "....dbsrv7.exe" not "....dbeng7.exe".
e.  On Network tab, verify check box "TCP/IP" is unchecked.  Verify "Shared memory" is checked.
f.  Click "OK"

a.  Select BallotNow Security under System DSN tab.  Press Configure...
b.  Verify Data source name is BallotNow Security under ODBC tab
c.  On Login tab, verify User ID is "dba" & password is "resolve".  Check "encrypt password" box.
d.  On Database tab, verify Server Name is BNSecurityServer.  Start line should be modified to launch "....dbsrv7.exe" not "....dbeng7.exe".
e.  On Network tab, verify check box "TCP/IP" is unchecked.  Verify "Shared memory" is checked.
f.  Click "OK"
  

4.  To authorize multiple licenses for the database server, execute the following in a command line window on the BN server:

dblic -u2 "dbsrv7.exe" "HIC" "Hart"

5.  Share the bn executable directory on the server, this is needed so the BNIP client can map to it.

6.  Map drive Z: on the BNIP client to the shared BN executable directory on the BN server.  You may need to do this using the IP address of the BN server machine, for example "\\192.162.0.1\Ballot Now".  Usually this is only necessary when running BNIP on the same machine as Ballot Now.

7.  To test proper ODBC connectivity, launch BN on the BN server.  On the BNIP client, run the ODBC Administrator.  Double click BallotNow Local on System DSN tab, and then at the bottom click Test Connection.  Connection should be successful.  Repeat for BallotNow Server.

8.  To test proper Z: drive mapping, Explore drive Z: on the BNIP client.  You should see all the files in the Ballot Now directory on the BN Server machine.



