----------------------------------------------------------------------------------
-- name:    readme.txt
-- purpose: install instructions for Viz|Content Pilot 5.0 application schema
-- author:	Bjarte Brandt (bbrandt@vizrt.com)
-- date:	01.06.2005
-- remarks:
----------------------------------------------------------------------------------

introduction
------------

In previous versions of Viz|Content Pilot (<4.0), only two oracle script-files
where required (vcp_ddl1_XX.sql, vcp_ddl2_XX.sql).

Viz|Content Pilot version 5.0 and onwards, several files are required to successfully 
install the application schema.
Business logic has been moved from the Viz|Content Pilot client and onto the 
Oracle Database. The logic is put into oracle packages.

All script files will be bundled into a zip file. (install_vcpXX.zip). Please
unzip all files into one folder unless you have configured your environment to
have SQL*Plus to look for files in specified folders through the environment 
variable: SQLPATH. 
SQL*Plus will first look for files in current folder, 
thereafter check the environment variable SQLPATH.

Winzip filename
---------------

install_vcp50.VERSION.zip

Remember to download the correct package for your platform.

Content
-------

1. Install the application schema
2. Upgrade from a previous version of Viz|Content Pilot
3. Install for advanced users
4. Administration



1. Install the application schema
---------------------------------

Please unzip these files to your favorite folder like "C:\oracle\scripts"

On Windows platform open a DOS shell:

C:\oracle\scripts\schema>

login to the database with sqlplus:

C:\oracle\scripts\schema>sqlplus username/password@tns_alias

create tablespace and users, interactive script

SQL>@install1_50.sql

please follow the instructions

create all schema objects (tables, indexes, triggers, views, packages etc...)

SQL>@install2_50.sql

Please follow the instructions. All other files will be called from within this
file to install the packages.
If the script should fail please review the log-file created.  


2. Upgrade from a previous version of Viz|Content Pilot
-------------------------------------------------------

Upgrade to Viz|Content Pilot 5.0 is only possible from Viz|Content Pilot 4.0

Please run script "upgrade_40_50.sql" and follow the instructions.


3. Install for advanced users (install into a non-default schema)
-----------------------------------------------------------------

You can install the Viz|Content Pilot application schema into a different schema
other then the default "PILOT". This can be very useful if you would like to have two
versions of Viz|Content Pilot installed on the same oracle database. 

alter session set current_schema = <SCHEMA_NAME> is not supported in the 
Viz Content Pilot client yet. A logon trigger can be used:

CREATE OR REPLACE TRIGGER logon_trg
after 
logon on schema
begin
  execute immediate 'alter session set current_schema = MY_SCHEMA';
end;

4. Administration
-----------------------------------------------------------------

Introduction
------------
In the folder "admin" there are several scripts you can run to 
administer users, roles, jobs etc...
Note! Do not run any of these script unless you are sure of the
they can do fo you. Please read the header information for each
script-file before execution.

Purge Expired Messages
----------------------
Purge expired messages from Viz|Content Pilot message queue.
Expired messages are transferred to the exception queue. 
They need to be explicitly removed running a job at regular interval (every day)

SQL>@create_vcp_message_queue_purge_job

Please accept the default input values unless you have installed the
application schema into a different schema than 'PILOT'.

Message Queue
-------------

In order to enable the vcp notification mechanism utilizing "Oracle Streams and
Advanced Queuing", some triggers need to be enabled. The Media Sequencer can
subscribe to messages posted on the message queue.

SQL>@alter_vcp_message_triggers
schemaname: <owner of the triggers> //press enter for default
operation: <enable/disable> //press enter for default 





  
