Page History
...
- Unix
- Default Location:
/var/sos-berlin.com/js7/joc/resources/joc
- A different location for the configuration directory can be specified during installation.
- Default Location:
- Windows
- Default Location:
C:\ProgramData\sos-berlin.com\js7\controller\<controller-id>\config\license
- where
<controller-id>
is the unique identifier for the Controller that is specified during installation.
- where
- A different location for the configuration directory can be specified during installation.
- Default Location:
- Find examples for Hibernate configuration from the JS7 - Database article.
Check Instance Settings
When installing JOC Cockpit then for each instance a title and ordering can be specified that become visible with the JS7 - Dashboard:
- Use a different title for each JOC Cockpit instance to better distinguish instances in the dashboard.
- Use an ordering of your choice that determines the sequence by which JOC Cockpit instances are displayed with the dashboard.
Both settings are used from the joc.properties
file, find the following example:
Code Block | ||||
---|---|---|---|---|
| ||||
################################################################################
### If JOC Cockpit is used in a cluster then specify a title to identify which node
### is currently used. Further specify the ordering (Primary <= 0, Standby > 0) for
### display of JOC Cockpit instances with the Dashboard view.
title = PRIMARY JOC COCKPIT
ordering = 0 |
Find the joc.properties
file from the following location:
- Unix
- Default Location:
/var/sos-berlin.com/js7/joc/resources/joc
- A different location for the configuration directory can be specified during installation.
- Default Location:
- Windows
- Default Location:
C:\ProgramData\sos-berlin.com\js7\controller\<controller-id>\config\license
- where
<controller-id>
is the unique identifier for the Controller that is specified during installation.
- where
- A different location for the configuration directory can be specified during installation.
- Default Location:
Adding License Key and Licensed Binary Code
...
In your browser navigate to the JOC Cockpit URL and enter the User Account and Password. Typically the URL includes the hostname and port that JOC Cockpit has been installed for:
For example,
http://myhost:4446
. Please check that the JOC Cockpit port is accessible which might include to add firewall rules to allow access to this port from the computer that you operate the browser for.After initial installation of JOC Cockpit the default User Account
root
and Passwordroot
will be available if no changes have been made to theshiro.ini
configuration file.
Note that the
root
user is assigned theall
role in the default configuration that includes any available permissions.
See the Authentication and Authorization - Configuration article for information about the configuration of other user profiles and authentication methods.Note that the JOC Cockpit web service might take a minute to start and to display the login window.
...