Page History

...

SOS performs >5000 regression tests when it comes to compatibility of Java, DBMS and JDBC Driver versions. The DBMS and JDBC Driver versions Versions stated above are included with SOS regression testing. If a specific version is not stated above then this doesn't mean that JS7 will not work with this version, it means that this version is not included with SOS regression testing. SOS does support use of newer DBMS and JDBC Driver versions not stated above as long as users prove that they are operated in a compatibility mode that corresponds to one of the versions stated above.

...

# add account
CREATE USER 'jobscheduler'@'%' IDENTIFIED BY 'jobscheduler';

Permissions

The following permissions are required for the schema:

...

• Tables, Views, Functions, Stored Procedures: CREATE, DROP, ALTER

In case that separate owner accounts and run-time accounts should be used for database access it is recommended to first create the database objects using the owner account and then to perform the installation of JOC Cockpit using the run-time account:

• Connect to the database using a MariaDB® / MySQL® client and the owner account.
• Run the mysql.sql script that is available from the db sub-directory when extracting the JOC Cockpit installer .tar.gz/.zip archive.

Permissions

The following permissions are required for the schema:

• to manage objects
  • Tables, Views, Functions, Stored Procedures: CREATE, DROP, ALTER
• to access objects at run-time
  • Tables, Views: SELECT, INSERT, UPDATE, DELETE
  • Functions, Stored Procedures: EXECUTE
    
    

...

# grant all permissions
GRANT ALL ON js7.* TO 'jobscheduler'@'%';

# alternatively grant individual permissions
GRANT CREATE, DROP, ALTER, EXECUTE, SELECT, UPDATE, INSERT, DELETE on js7.* to 'jobscheduler'@'%';

...

# set up database
CREATE DATBASE JS7
...
CHARACTER SET AL32UTF8;

# consider linguistic sorting for Unicode with WHERE clauses
ALTER SESSION SET NLS_COMP='LINUGUISTIC';

# consider linguistic sorting for Unicode with ORDER BY clauses
ALTER SESSION SET NLS_SORT='LINUGUISTIC';

Note:

• Consider that NLS_COMP and NLS_SORT have to use the same value.

...

# add owner account
CREATE USER JS7_OWNER IDENTIFIED BY JS7_OWNER;
GRANT CONNECT, RESOURCE TO JS7_OWNER;

# add run-tine account
CREATE USER JS7_USER IDENTIFIED BY JS7_USER;
GRANT CONNECT, RESOURCE TO JS7_USER; CONNECT, RESOURCE TO JS7_USER;

In case that separate owner accounts and run-time accounts should be used it is recommended to first create the database objects using the owner account and then to perform the installation of JOC Cockpit using the run-time account:

• Connect to the database using an Oracle® client and the owner account.
• Run the oracle.sql script that is available from the db sub-directory when extracting the JOC Cockpit installer .tar.gz/.zip archive.

Permissions

The following permissions are required for JS7:

...

# set up database
CREATE DATABASE JS7
ENCODING 'UTF8'
LC_COLLATE = 'en_US.UTF-8'
LC_CTYPE = 'en_US.UTF-8';

Accounts

A user account is created in PostgreSQL®, for example:

...

...

UTF-8'
LC_CTYPE = 'en_US.UTF-8';

Accounts

A user account is created in PostgreSQL®, for example:

# add an account
create user JS7_USER with password 'JS7_USER';

In case that separate owner accounts and run-time accounts should be used for database access it is recommended to first create the database objects using the owner account and then to perform the installation of JOC Cockpit using the run-time account:

• Connect to the database using a PostgreSQL® client and the owner account.
• Run the pgsql.sql script that is available from the db sub-directory when extracting the JOC Cockpit installer .tar.gz/.zip archive.

Permissions

The following permissions are required for the schema:

...

# create a role
create role JS7_ROLE WITH LOGIN;

# grant permissions as specified above to the role
grant USAGE on schema public to JS7_ROLE;
 
grant SELECT,UPDATE,INSERT,DELETE on all tables in schema public to JS7_ROLE;
grant EXECUTE on all functions in schema public to JS7_ROLE;
grant CREATE on schema public to JS7_ROLE;

# assign the role to the user
 grant JS7_ROLE to JS7_USER;

...