Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Setup Foundation Elements for VetView

For running script files we recommend using a Database developer tool like SQL Developer or TOAD. This allows you to preview and update any script prior to executing it, it also allows you to see progress and any error messages.

Example Connection in SQL Developer                                          Example Connection in TOAD

                            

 

All script file should be executed using the VetView account.

There are 4 scripts that need to be run to prior starting up the VetView project on the Web Server

  1. Tables, Constraints, and Indices
    1. The Tables 0.9.x.sql file includes a single line statement that defines each table. Some tables that include CLOB columns have tablespace definition that may need to be replaced depending on the name of the tablespaces defined when setting up the database.
    2. Example Table Create Statement
      CREATE TABLE NOTIFICATIONS ( NOTIFICATION_ID NUMBER(19) NOT NULL, VERSION NUMBER(19) NOT NULL, CREATED_DATE TIMESTAMP(6), LUD TIMESTAMP(6), LUN VARCHAR2(30 CHAR), MESSAGE_TEXT CLOB NOT NULL, MSG_FROM NUMBER(19), MESSAGE_LINK NUMBER(19), MESSAGE_LINK_TYPE VARCHAR2(30 CHAR), MSG_TO NUMBER(19) NOT NULL, MESSAGE_TO_SECTION_LINK NUMBER(19), MESSAGE_TO_SERVICE_LINK NUMBER(19), MESSAGE_TYPE VARCHAR2(30 CHAR) NOT NULL, STATUS VARCHAR2(30 CHAR) NOT NULL ) 
      LOB (MESSAGE_TEXT) STORE AS ( TABLESPACE DATA_SMALL ENABLE STORAGE IN ROW CHUNK 8192 RETENTION);
      
      CREATE INDEX NOTIFICATIONS_MSG_FROM_INDEX ON NOTIFICATIONS (MSG_FROM);
      
      CREATE INDEX NOTIFICATIONS_MSG_TO_INDEX ON NOTIFICATIONS (MSG_TO);
      
      ALTER TABLE NOTIFICATIONS ADD (  PRIMARY KEY (NOTIFICATION_ID) ENABLE VALIDATE);
      
      ALTER TABLE NOTIFICATIONS ADD (  CONSTRAINT FK4BD694E880B55DEB FOREIGN KEY (MSG_FROM) REFERENCES EMPLOYEE (EMP_ID) ENABLE VALIDATE,  CONSTRAINT FK4BD694E88DBFBC3C FOREIGN KEY (MSG_TO) REFERENCES EMPLOYEE (EMP_ID) ENABLE VALIDATE);
  2. Sequences
    1. Example Sequence Statement
      CREATE SEQUENCE SEQ_ACCESSION_COMMENT_ID START WITH 1 MAXVALUE 9999999999999999999999999999 MINVALUE 1 NOCYCLE CACHE 20 NOORDER;
  3. Localization
    1. Localization is a table of labels and messages used to display dynamically on the rendened web pages by language. The localization script loads up the default set of text which is in English. The "Localization All 0.9.x.sql" file deletes all existing records in the table and resets it for the indicated version.
    2. Example Localization Statement
      Insert into LOCALIZATION (ID, VERSION, CODE, DATE_CREATED, LAST_UPDATED, LOC, RELEVANCE, TEXT)
       Values (1464, 0, 'privilege.description.worksheet', TO_TIMESTAMP('8/3/2012 11:10:31.562000 AM','fmMMfm/fmDDfm/YYYY fmHH12fm:MI:SS.FF AM'), TO_TIMESTAMP('8/3/2012 11:10:31.562000 AM','fmMMfm/fmDDfm/YYYY fmHH12fm:MI:SS.FF AM'), '*', 1, 'Worksheet Screen');
  4. Security Roles and Admin User Account
    1. The security roles are the defined access and privileges that are defined by VetView. These are not the institution defined user roles, those are defined from a setup screen inside of the application. The second part of the script defines an administrator employee record and security user with all defined roles associated to it. By default the username is administrator and the password is 'VETVIEW-ADMIN'. User Accounts are not created in or user to connect to the oracle database. User accounts can either use a database encrypted password or LDAP for authentication. The VetView web application always connects to the database using the VetView oracle user account.
    2. Example Administrator Statement
      INSERT INTO EMPLOYEE ( emp_id, version, username, display_name, cell_messages, cell_notifications, dvm_YN, email_messages, email_notifications, default_home_page, language, faculty_yn, intern_yn, resident_yn, staff_yn, student_yn, tech_yn, service_chief_yn, assignto_yn,coordinator_yn, signature_yn )
      Values (  seq_emp_id.nextval, 1, 'ADMINISTRATOR', 'Administrator', 'N', 'N', 'N', 'N', 'N', 'Lab', 'en_US', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N' ) ;
               
      SELECT HIBERNATE_SEQUENCE.nextval INTO v_sec_user_id FROM dual ;
           
      INSERT INTO SEC_USER ( id, version, account_expired, account_locked, authentication_type, enabled, failedlogincount, "password", password_expired, system_to_system_identifier, username, session_exempt ) Values ( v_sec_user_id , 1, 0, 0, 'Local Account', 1, 0, '2dec8726b8e5f64cb8b86cf4839f76669ab3945fbea4b9eeef6adb0169287dc7c2063d5c567b2006c8b2ff3bea3fdee1abcde9eaddb45a02dff1214e69c34e2a', 0, 'cbdc5ae8e5bc4b5da0abe67faa9d6ad1', 'ADMINISTRATOR', 0 ) ;
           
      INSERT INTO SEC_USER_SEC_ROLE s ( S.SEC_USER_ID, S.SEC_ROLE_ID ) SELECT v_sec_user_id, R.ID FROM sec_role r ;
     

 

 


Next Step

Previous Step


  • No labels