Install ServiceSWAT Installation Instructions Database Specific Oracle
Set up the following system environment variable:
LOCAL = <tns for SERVICESscheduling and SWAT DBs>.
For example:
- Right-click My Computer, click Properties, click Advanced, click Environment Variables, click New under System Variable.
- Variable name: LOCAL
- Variable value: <tns for SERVICESscheduling and SWAT DBs>
- Click OK
Create the SWAT Console Database User in the same Oracle instance as the ServiceScheduling schema. This user should have the same permissions as are required for the ServiceScheduling database user.
Sample SQL to create user:
CREATE USER <SWAT_CONSOLE> IDENTIFIED BY <SWAT_CONSOLE> DEFAULT TABLESPACE <TS01> TEMPORARY TABLESPACE <TEMP> QUOTA unlimited ON <TS01>; GRANT spdev TO <SWAT_CONSOLE>
As an example use USERS instead of <TS01> and temp instead of <TEMP>:
Ensure that the properties file is updated with the swat console users value entered above:- “console_username” and “console_password”.
The values in the properties file are used by the perl scripts to add permissions to database users during setup of the swat instance.
Run <installation directory>\webapps\ServiceSWAT\database\SWAT-runall-Once.sql against SWAT Console Schema
sqlplus <console username/console password> @SWAT-runall-Once.sql
Import the zip grouping table into the SWAT Console Schema. In the database directory there is an export of this table called swat_zip_group.dmp.
Imp userid=<swat_console user>/<swat_console_password> file=swat_zip_group.dmp commit=y ignore=y fromuser=swat_console touser=<swat_console user>
Importing the zip grouping table is only required when running SWAT against a USA-based customer.