|
On
the POS BackOffice machine
Set up the POS BackOffice machine
to communicate with SiteManager over a network (follow
these steps even if the two software packages are on the
same machine):
1.
Set the Host Communication Type to Network.
2.
Open Control Panel
3.
Select ODBC Data Sources. In Windows 2000 this
is under Administrative Tools
4.
Select the System DSN tab
5.
Add a SQL Server data source
6.
Set the Name to SiteManager.
7.
Set the Server to local if itÕs the
database is on this machine. Otherwise, Set Server to
the machine where the SiteManager SQL database is located.
8.
Choose NT authentication if the database is on
this machine. Otherwise choose SQL Server authentication.
(If you choose SQL Server authentication, you must specify
a user id and password that SQL Server will recognize
and set global settings 141 and 142 to match the SQL user
id and password you have specified. If using Windows NT
authentication, leave options 141 and 142 blank.)
9.
ÔChange the default database to:Õ SiteManager.
10.
Finish.
Global Settings
School
Name (Global Setting 2)
Set the
school name. This will be a key field in any communication
with SiteManager.
Host Communication
Type (Global Setting 140)
Host Communication
settings tell BackOffice whether to communicate with SiteManager
by file, over a network, or not at all. The values
for this setting are Network, File, and
None. The database ships with this setting
set to None.
Host Communication
Database User ID (Global Setting 141)
If Host
Communication Type is set to Network, this setting supplies
the User ID needed to log in to SQL Server. It will
usually be sa (for SQL authentication), blank for
NT authentication. The database ships with this
setting set to sa. This setting can be ignored
when Host Communication Type is set to File or None.
Host Communication
Database Password (Global Setting 142)
If Host
Communication Type is set to Network, this setting supplies
the Password needed to log in to SQL Server. It
will usually be admin (for SQL authentication),
blank for NT authentication. The database ships
with this setting set to admin. This setting
can be ignored when Host Communication Type is set to
File or None.
Host Communication
(Communicate Participant) (Global Setting 144)
If SiteManager
is to house the master district student information for
POS then this setting should be set to True. Data
will flow both from the SiteManager database to the POSBO
database, updating POS with changes made in SiteManager,
and from POSBO to the SiteManager database, updating SiteManager
with changes made at the POSBO site. If changes are made
on both ends then, the change which is dated the latest
will have precedence.
Participant Status
Set
up the Participant Statuses as desired. This list must
be matched in SiteManager.
Serving
Periods
Set
up the Serving Periods as desired. This list must be matched
in SiteManager.
On
the SiteManager machine
General
Maintenance / Agency Administration
Set up Programs
under the desired Agency (or Agencies) with ÔImport KeysÕ
matching the Serving Periods in POS BackOffice. In other
words, if you have a Serving Period set up in POS then
it must be represented in the Agency Programs table. The
Agency / Programs / Import Key and POS Back Office Serving
Periods must match identically (they are case sensitive).
General
Maintenance / Site Administration
Set up a site
with the [Site] Import Key setting set the same as POSBO
Golbal Setting #2. This is also case-sensitive.
Settings
/ Participant Status
Set up Participant
Statuses in SiteManager to match identically. They need
to have the same ÔStatus IDÕ as POS BackOffice and/or
be in the same order).
|
FAQ
