Page History

...

The Deployment Server is used for the following purposes:

• to hold the script environment for JS7 - Automated Installation and Update and the JS7 - Deployment Packaging Script,
• to hold the configuration files and certificates for deployment with JS7 components,
• to hold the JS7 installation files per JS7 release and component such as JOC Cockpit, Controller, Agent,
• to hold the archive of deployment packages per JS7 releases and target machine,
• to operate a JS7 Agent that is used to perform the JS7 - Deployment Workflow.

...

• archive (holds deployment packages)
  • <deployment-descriptor> (specifies the Deployment Descriptor)
    • agents (holds Agent deployment packages)
      • <agent-id>(specifies the Agent ID)
        • js7_deploy_agent_unix.<agent-id>.<release>.config.tar.gz (deployment package for the Agent's configuration directory)
        • js7_deploy_agent_unix.<agent-id>.<release>.install.tar.gz (deployment package for the Agent's installation directory)
        • run_deploy_agent.sh (deployment script)
        • run_install_agent.sh (wrapper script for parameterized call to js7_install_agent.sh)
      • <agent-id>(specifies the Agent ID)
      • ...
    • controllers (holds Controller deployment packages)
      • <controller-id> (specifies the Controller ID)
        • <controller-type> (specifies the type of the Controller instance which is primary or secondary) 
          • js7_deploy_controller_unix.<controller-id>.<controller-type>.<release>.config.tar.gz (deployment package for the Controller instance's configuration directory)
          • js7_deploy_controller_unix.<controller-id>.<controller-type>.<release>.install.tar.gz (deployment package for the Controller instance's installation directory)
          • run_deploy_controller.sh (deployment script)
          • run_install_controller.sh (wrapper script for parameterized call to js7_install_controller.sh)
        • <controller-type> (specifies the type of the Controller instance which is primary or secondary) 
    • js7_import_tar.gz (holds the Deployment Workflow for import to JS7 JOC Cockpit)
  • <deployment-descriptor> (specifies the Deployment Descriptor)
  • ...
• bin (holds executable files, preferably individual scripts, deployment scripts and installer scripts available from JS7 - Download)
  • js7_create_certificate_store.sh (used to add certificates to keystores and truststores, see JS7 - How to add SSL TLS Certificates to Keystore and Truststore)
  • js7_create_deployment_package.sh (used to create deployment packages, see JS7 - Deployment Packaging Script)
  • js7_install_agent.sh (used to install Agents, see JS7 - Automated Installation and Update of Agent)
  • js7_install_controller.sh (used to install Controller instances, see JS7 - Automated Installation and Update of Controller)
  • js7_install_joc.sh (used to install JOC Cockpit instances, see JS7 - Automated Installation and Update of JOC Cockpit)
• ca  (holds the Certificate Authority as explained from  JS7 - How to create self-signed Certificates, not used if an external Certificate Authority is in place)
  • certs (holds CA-signed Certificates)
  • csr (holds Certificate Signing Requests)
  • private (holds Private Keys)
• config (holds configuration files)
  • agents (holds Agent configuration files)
    • instances (holds configuration files specific for an Agent)
      
      • <agent-id>(specifies the Agent ID for directories and files that are specific to an Agent)
        • config (general configuration)
          • private (specific configuration)
            • trusted-pgp-keys (optionally holds PGP public key files and keyring files used for signing, see JS7 - Deployment of Scheduling Objects)
              • <pgp-public-key> (public key file or keyring file)
              • <pgp-public-key> (public key file or keyring file)
              • ...
            • trusted-x509-keys (optionally holds X.509 certificate files used for signing, see JS7 - Deployment of Scheduling Objects)
              • <x509-certificate> (X.509 certificate file)
              • <x509-certificate> (X.509 certificate file)
              • ...
            • https-keystore.p12 (optional default location and file name of a PKCS12 truststore)
            • https-truststore.p12 (optional default location and file name of a PKCS12 truststore)
            • private.conf (optional configuration file, for example to specify keystore, truststore and Distinguished Names of Controller certificate, see JS7 - Agent Configuration Items)
            • log4j2.xml (optional log configuration file, see JS7 - Log Levels and Debug Options)
          • agent.conf (optional configuration file, see JS7 - Agent Configuration Items)
      • <agent-id>(specifies the Agent ID for directories and files that are specific to an Agent)
      • ...
    • templates (holds configuration files that act as templates for a number of Agents)
      • <ag
    certs (holds certificate files for deployment with Agents and Controllers)
  • ca  (optional Root Certificate Authority used for self-signed certificates)
    • <root-ca-certificate> (the Root CA Certificate file, frequently available with a .pem, .crt extension)
  server (Server Authentication Certificates)<server-certificate>^{(Server Certificate file, frequently available with a .pem, .crt extension)}<server-certificate>^{(Server Certificate file, frequently available with a .pem, .crt extension)}
  • ^....
  client (Client Authentication Certificates)<client-certificate>^{(Client Certificate file, frequently available with a .pem, .crt extension)}<client-certificate>
  • • <template-name> (arbitrary directories for templates can be used)
      • config (general configuration)
        • private (specific configuration)
          • trusted-pgp-keys (optionally holds PGP public key files and keyring files used for signing, see JS7 - Deployment of Scheduling Objects)
            • ...
          • trusted-x509-keys (optionally holds X.509 certificate files used for signing, see JS7 - Deployment of Scheduling Objects)
            • ...
    • <template-name> (arbitrary directories for templates can be used)
    • ...
  • certs (holds certificate files for deployment with Agents and Controllers)
    • ca  (optional Root Certificate Authority used for self-signed certificates)
      • <root-ca-certificate> (the Root CA Certificate file, frequently available with a .pem, .crt extension)
    • server (Server Authentication Certificates)
      • <server-certificate>^{(Server Certificate file, frequently available with a .pem, .crt extension)}
      • <server-certificate>^{(Server Certificate file, frequently available with a .pem, .crt extension)}
      • ^....
    • client (Client Authentication Certificates)
      • <client-certificate>^{(Client Certificate file, frequently available with a .pem, .crt extension)}
      • <client-certificate>^{(Client Certificate file, frequently available with a .pem, .crt extension)}
      • ...
  • controllers (holds Controller configuration files)
    • instances (holds configuration files specific for a Controller instance)
      • <controller-id>.<controller-type>(specifies the Controller ID for directories and files that are specific to a Controller instance with the instance type being primary or secondary)
        • config (general configuration)
          • private (specific configuration)
            • trusted-pgp-keys (optionally holds PGP public key files and keyring files used for signing, see JS7 - Deployment of Scheduling Objects)
              • <pgp-public-key> (public key file or keyring file)
              • <pgp-public-key> (public key file or keyring file)
              • ...
            • trusted-x509-keys (optionally holds X.509 certificate files used for signing, see JS7 - Deployment of Scheduling Objects)
              • <x509-certificate> (X.509 certificate file)
              • <x509-certificate> (X.509 certificate file)
              • ...
            • https-keystore.p12 (optional default location and file name of a PKCS12 truststore)
            • https-truststore.p12 (optional default location and file name of a PKCS12 truststore)
            • private.conf (optional configuration file, for example to specify keystore, truststore and Distinguished Names of JOC Cockpit certificate, see JS7 - Controller Configuration Items)
            • log4j2.xml (optional log configuration file, see JS7 - Log Levels and Debug Options)
          • controller.conf (optional configuration file, see JS7 - Controller Configuration Items)
      • <controller-id>.<controller-type>(specifies the Controller ID for directories and files that are specific to a Controller)
      • ...
    • templates (holds configuration files that act as templates for a number of Agents)
      • <template-name> (arbitrary directories for templates can be used)
        • config (general configuration)
          • private (specific configuration)
            • trusted-pgp-keys (optionally holds PGP public key files and keyring files used for signing, see JS7 - Deployment of Scheduling Objects)
              • ...
            • trusted-x509-keys (optionally holds X.509 certificate files used for signing, see JS7 - Deployment of Scheduling Objects)
              • ...
      • <template-name> (arbitrary directories for templates can be used)
      • ...
  • joc  (holds JOC Cockpit configuration files)
    • instances (holds configuration files that are specific for a JOC Cockpit instance)
      • <server>.<instance-type> (holds configuration files for a JOC Cockpit instance running on a specific server with the instance type being primary or secondary)
        • resources (optionally holds configuration such as the joc.properties file, keystore, truststore files etc.)
        • response (holds response files, mainly the joc_install.xml response file, that are copied to the JOC Cockpit's setup directory)
      • <server>.<instance-type> (holds configuration files for a JOC Cockpit instance running on a specific server with the instance type being primary or secondary)
      • ...
    • templates (holds configuration files that act as templates for a number of JOC Cockpit instances)
      • <template-name> (arbitrary directories for templates can be used)
        • resources (optionally holds configuration such as the joc.properties file, keystore, truststore files etc.)
        • response (holds response files, mainly the joc_install.xml response file, that are copied to the JOC Cockpit's setup directory)
      • <template-name> (arbitrary directories for templates can be used)
      • ...
    ^{(Client Certificate file, frequently available with a .pem, .crt extension)}
  • ...
  controllers<controller-id>(specifies the Controller ID for directories and files that are specific to a Controller)joc
• desc (holds Deployment Descriptors)
  • <deployment-descriptor>.json (Deployment Descriptor .json file)
  • <deployment-descriptor>.json (Deployment Descriptor .json file)
  • ...
• release  (holds the installation tarballs for JS7 releases)
  • ... (users can apply an arbitrary directory hierarchy at this level)
    
    • js7_agent_unix.<release>.tar.gz (JS7 Agent installation tarball as download from the SOS Web Site)
    • js7_controller_unix.<release>.tar.gz (JS7 Controller installation tarball as download from the SOS Web Site)
    • js7_joc_linux.<release>.tar.gz (JS7 JOC Cockpit installation tarball as download from the SOS Web Site)
• work (the working area is preferably used to perform installation of JS7 components during packaging)
  • agents (directory for Agent installation during packaging)
    • <agent-id>(specifies the Agent ID for directories and files that are specific to an Agent)
      • ... (sub-directory used for Agent installation)
    • <agent-id>(specifies the Agent ID for directories and files that are specific to an Agent)
    • ...
  • controllers (directory for Controller installation during packaging)
    • <controller-id>(specifies the Controller ID for directories and files that are specific to a Controller)
      • ... (sub-directory used for Controller installation)
    • <controller-id>(specifies the Controller ID for directories and files that are specific to a Controller)
    • ...
  • tmp (temporary files are written to this directory, if the --keep-work switch is used when invoking the JS7 - Deployment Packaging Script then files will remain in this directory which suggests cleanup by the user)
• env.sh (Environment Script, see next chapter)

...