Page History
...
In a first step users have to create a database schema and account for JS7. The database schema has to support the Unicode character set.
The following chapters provide some common examples that are not complete and not exhaustive. Database administrators might apply their standards how to setup a database for JS7.
Setup for MariaDB®/ MySQL®
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
# 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'@'%'; |
Setup for Oracle®
For secure connections without use of passwords consider information from JS7 - How to connect JOC Cockpit to an Oracle database without using passwords.
Database
When creating the database then consider to use UTF based character encoding and a collating sequence that supports UTF, for example:
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
# 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; |
Connection Pool
Setup for SQL Server®
For secure connections without use of passwords consider information from JS7 - How to connect to an SQL Server database without using passwords.
Database
When creating the database then consider to use a UTF based character encoding and collating sequence, for example:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
# set up database
CREATE DATABASE JS7
...
COLLATE LATIN1_GENERAL_100_CI_AS_SC_UTF8; |
Accounts
A user account is created in SQL Server®, for example:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
# 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 an SQL Server® client and the owner account.
- Run the
mssql.sql
script that is available from thedb
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
- Tables, Views, Functions, Stored Procedures:
- to access objects at run-time
- Tables, Views:
SELECT, INSERT, UPDATE, DELETE
- Functions, Stored Procedures:
EXECUTE
- Tables, Views:
Connection Pool
JS7 makes use of a connection pool to allow a larger number of JS7 makes use of a connection pool to allow a larger number of JOC Cockpit user sessions to share database connections from the pool.
...
JOC Cockpit Component | Min. Connections | Max. Connections | Configurable | Comment |
---|---|---|---|---|
JS7 - REST Web Service API | 10 | unbounded | yes | Recommendation: no. of simultaneous users / 3. This number counts per JOC Cockpit instance. |
1 | 1 | no | ||
JS7 - Cleanup Service | 5 | 5 | no | |
JS7 - Daily Plan Service | 1 | 1 | no | |
JS7 - History Service | 1 | number of connected Controller Instances | no | Any Controllers connected to a JOC Cockpit Instance are counted. |
JS7 - Monitor Service | 3 | 3 | no | 2 connections for monitoring. 1 connection for notifications. |
...