Ubik Batch Server Installation Guide
From UbikWiki
Line 1: |
Line 1: | ||
[[Category:Ubik Batch Server]] | [[Category:Ubik Batch Server]] | ||
| - | {| class="prettytable" | ||
| - | | <center>BATCH Server Installation Guide</center> | ||
| - | |||
| - | |} | ||
| - | <center>[#1.Batch Server:|outline 1 Batch Server:3]</center> | ||
| - | |||
| - | [#1.1.Requirements:|outline 1.1 Requirements:3] | ||
| - | |||
| - | [#1.1.1.JDK|outline 1.1.1 JDK3] | ||
| - | |||
| - | [#1.1.2.Database|outline 1.1.2 Database3] | ||
| - | |||
| - | [#1.2.Batch Server Installation steps:|outline 1.2 Batch Server Installation steps:3] | ||
| - | |||
| - | [#1.2.1.Create the Database:|outline 1.2.1 Create the Database:3] | ||
| - | |||
| - | [#1.2.2.Launch the installer:|outline 1.2.2 Launch the installer:3] | ||
| - | |||
| - | [#1.2.3.Installing from properties file|outline 1.2.3 Installing from properties file10] | ||
| - | |||
| - | [#1.2.4.After installation|outline 1.2.4 After installation12] | ||
| - | |||
| - | [#1.2.5.Test installation|outline 1.2.5 Test installation12] | ||
| - | |||
| - | [#1.3.Batch Server Uninstallation steps:|outline 1.3 Batch Server Uninstallation steps:13] | ||
| - | |||
| - | [#1.3.1.Go to <INSTALL_DIRECTORY>/bin|outline 1.3.1 Go to <INSTALL_DIRECTORY>/bin13] | ||
| - | |||
| - | [#1.3.2.Run uninstallConsoleBatchService.bat|outline 1.3.2 Run uninstallConsoleBatchService.bat13] | ||
| - | |||
| - | [#1.4.Batch Server Configuration options:|outline 1.4 Batch Server Configuration options:13] | ||
| - | |||
| - | [#1.4.1.General configuration|outline 1.4.1 General configuration13] | ||
| - | |||
| - | [#1.4.2.JMX connectivity|outline 1.4.2 JMX connectivity14] | ||
| - | |||
| - | [#1.4.3.Database connectivity|outline 1.4.3 Database connectivity14] | ||
| - | |||
| - | [#1.4.4.Mailer connectivity|outline 1.4.4 Mailer connectivity14] | ||
| - | |||
| - | [#1.4.5.Logging configuration|outline 1.4.5 Logging configuration14] | ||
| - | |||
| - | [#1.5.Cold deployment|outline 1.5 Cold deployment15] | ||
| - | |||
| - | [#1.5.1.How To|outline 1.5.1 How To15] | ||
| - | |||
| - | [#1.5.2.JNDI Mapping Customization |outline 1.5.2 JNDI Mapping Customization 15] | ||
| - | |||
| - | [#1.5.3.What it does|outline 1.5.3 What it does16] | ||
| - | |||
| - | <center>[#2.Batch Administration Webapp:|outline 2 Batch Administration Webapp:16]</center> | ||
| - | |||
| - | [#2.1.Create the Database using this script:|outline 2.1 Create the Database using this script:16] | ||
| - | |||
| - | [#2.2.PERMIT tasks|outline 2.2 PERMIT tasks17] | ||
| - | |||
| - | [#2.3.Deploy the EAR batchadmin-XXX.ear.|outline 2.3 Deploy the EAR batchadmin-XXX.ear.18] | ||
| - | |||
| - | [#2.3.1.Map the pools:|outline 2.3.1 Map the pools:18] | ||
| - | |||
| - | [#2.4.Adding a Batch Server:|outline 2.4 Adding a Batch Server:18] | ||
| - | |||
| - | [#2.4.1.Open menu Configuration > Manage Consoles|outline 2.4.1 Open menu Configuration > Manage Consoles18] | ||
| - | |||
| - | [#2.4.2.Add a Server|outline 2.4.2 Add a Server18] | ||
| - | |||
| - | [#2.4.3.Fill this form|outline 2.4.3 Fill this form19] | ||
| - | |||
| - | [#2.4.4.Finish the Step|outline 2.4.4 Finish the Step19]= Batch Server: = | ||
== Requirements: == | == Requirements: == | ||
=== JDK === | === JDK === | ||
Revision as of 14:08, 4 November 2007
Requirements:
JDK
First install a JDK 5 or an upper version:
Install only JDK (JRE, demo and source code are not necessary).
Install in directory E:\local\jdk1.5.x_xx
The location will be further referenced as <JAVA_HOME>
The installation procedure requires the following elements:
- LAST_VERSION\installer\console-install-pack-4.0.0.x.jar
- LAST_VERSION\scripts-sql\console-oracle.ddl
Database
You must have a dedicated schema to the repository server.
Batch Server Installation steps:
Create the Database:
Play the following script:
- [//nlasrc01/Tetrix/Deploiement/_console/console-4.0.0.1/scripts-sql/console-oracle.ddl LAST_VERSION][//nlasrc01/Tetrix/Deploiement/_console/console-4.0.0.1/scripts-sql/console-oracle.ddl \scripts-sql\console-oracle.ddl]
- [//nlasrc01/Tetrix/Deploiement/_console/LAST_VERSION/scripts-sql/console-oracle.dml LAST_VERSION\scripts-sql\console-oracle.dml]
Launch the installer:
Run the following command line:
| <JAVA_HOME>\bin\java –jar <Path_To_Installer>\ console-install-pack-4.0.0.x.jar |
This screen will appear:
[[Image:]]
Step 1
Click on next
[[Image:]]
Step 2
Click on next:
[[Image:]]
Step 3
Click on next:
[[Image:]]
Step 4: Installation Options
Fill in:
- Installation Directory: Path where the Batch server will be installed
- ID of the console: This ID must be unique and will be used in database to identify uniquely the Server Batches,…
[[Image:]]
Step 5: JMX Connectivity
Fill in:
- JNDI Name of the console: Path where the Batch server will be installed
- Port of the Naming Service: Check the chosen port is free
- Port of the JMX Service: Check the chosen port is free
[[Image:]]
Step 6: Server Repository Database parameters
Fill in:
- DB User: User of the Server Repository Database
- DB Password: Password of the Server Repository Database
- Class of the JDBC Driver
- URL of the JDBC Connection (ex : jdbc:oracle:thin:@nladbl01.preprod.org:1529:tetrix04)
[[Image:]]
Step 7: Embedded BAR Server Configuration
This step configures the BAR Upload server that is shipped inside the Batch Server. This server receives BARs that are sent by the Batch Admin Web Application
Fill in:
- BAR Server host: Host of the machine where the Batch Server will be running
- BAR Server Port: Port of the server (check the port is not used)
- BARs upload folder : Folder where the BARs will be stored
[[Image:]]
Step 8: Batch Server Logging Folder
This step configures the Root Folder for Logs. This folder will be further referenced as a JVM property called LOG_ROOT_PATH
Fill in:
- Logging directory
[[Image:]]
Step 9: Mailer configuration
This step configures the Mail notification system. Each time an error occurs a mail will be sent using the configured parameters
Fill in:
- Host of the mailer: Host of the Mail server
- Port of the mailer: Port of the Mail server (defaults to 25)
- Name of the mailer : Name the will appear in Mails
- Mail of administrator: Mail of the technical administrator (used only if XML storage is chosen)
[[Image:]]
Step 10 : Environment parameters
This step configures environment parameters; it will generate a setenv.bat (for Windows) and setenv.sh (for Linux)
Fill in:
- Name of the NT service (Identifies the NT service)
- JAVA_HOME: It must be a JDK 5
- JVM options: You may change –Xmx and –Xms and add other properties
[[Image:]]
End installation
Click on Next
[[Image:]]
Click on Next
[[Image:]]
Click on Install:
[[Image:]]
Installing from properties file
You have another option if you don’t want to re seize all options on each installation. The installer writes a file called “ant.install.properties” after each installation. This file contains all seized properties.
So you can use this properties file “ant.install.properties” for next installs, this file must be located in the folder from which you launch the installer.
To make the installer use it:
| <JAVA_HOME>\bin\java –jar <Path_To_Installer>\ console-install-pack-4.0.0.x.jar text-auto |
You will be asked:
| Installation configuration found. Load the existing configuration? |
Answer yes.
Example of a generated “ant.install.properties” file:
| ### Ant Installer - properties auto generated on Mon\ Aug\ 20\ 09\:45\:32\ CEST\ 2007
ant.install.config.version = 0.0
# .DirectoryInput INSTALL_DIRECTORY = D\:\\console-batch # .UnvalidatedTextInput CONSOLE_ID = Console4005
# .UnvalidatedTextInput CONSOLE_JNDI_NAME = Console # .ValidatedTextInput NAMING_SERVICE_PORT = 5001 # .ValidatedTextInput JMX_SERVICE_PORT = 5002
# .UnvalidatedTextInput DB_USER = console_batch4 # .UnvalidatedTextInput DB_PASSWORD = console_batch4 # .LargeSelectInput DB_DRIVER_CLASS = oracle.jdbc.OracleDriver # .UnvalidatedTextInput DB_URL = jdbc\:oracle\:thin\:@TLADBXD1.dktetrix.net\:1529\:tetrix01
# .UnvalidatedTextInput BAR_SERVER_HOST = localhost # .ValidatedTextInput BAR_TRANSFER_PORT = 5003 # .DirectoryInput BAR_UPLOAD_DIRECTORY = D\:\\console-batch\\bar-upload-directory
# .DirectoryInput LOG_DIRECTORY = D\:\\console-batch\\logs
# .UnvalidatedTextInput MAIL_HOST = 172.16.4.25 # .ValidatedTextInput MAIL_PORT = 25 # .UnvalidatedTextInput MAILER_NAME = CB4005 # .UnvalidatedTextInput ADMINISTRATOR_MAIL = admin@foo.com # .SelectInput MAIL_MANAGER_TYPE = salto.batch.system.MailManagerDBStore
# .UnvalidatedTextInput SERVICE_NAME = console-batch # .DirectoryInput JAVA_HOME = D\:\\JDKs\\jdk1.5.0_12 # .UnvalidatedTextInput JAVA_OPTS = -Xms256M -Xmx512M -XX\:MaxPermSize\=128m -DLOG_ROOT_PATH\=D\:\\console-batch\\logs
# .TargetInput install = true # Targets selected for page selector-targets = install,
# Targets selected for page progress-targets = cleanuptarget, |
After installation
Play the script generated by the installer in <INSTALL_DIRECTORY>/config/oracle-install.sql on the Repository Database
Copy the content of [//nlasrc01/Tetrix/Deploiement/_console/console-4.0.0.1/business/lib LAST_VERSION\business\lib] in folder <INSTALL_DIR>\business\lib
Test installation
Go to <INSTALL_DIRECTORY>/bin
Run console.bat
The JMX URL will be written in <INSTALL_DIRECTORY>/config/jmx-service-url.txt
If the server does not stop, your installation is OK.
You can now register the service by running:
<INSTALL_DIRECTORY>/bin/installConsoleBatchService.bat
If the server stops, see errors logs
Batch Server Uninstallation steps:
Go to <INSTALL_DIRECTORY>/bin
Run uninstallConsoleBatchService.bat
Batch Server Configuration options:
General configuration
This configuration is in file <INSTALL_DIRECTORY>/config/config.properties
Configuration parameters:
| Paramter | Description | Default Value |
| CONSOLE_ID | Unique ID Of the Batch Server | See 1.2.2.4 |
| INSTALL_DIR | <INSTALL_DIRECTORY> | See 1.2.2.4 |
| com.salto.console.PLUGIN_MANAGER_STORE | Type of storage for Plugins configuration | salto.batch.system.PluginManagerXMLStore |
| PLUGIN_MANAGER_FILE | Path to the file that contains general plugin | <INSTALL_DIRECTORY>/config/plugin-manager.xml |
| LOCK_DIR | ||
| CONFIG_ROOT | Path to configuration Folder | <INSTALL_DIRECTORY>/config |
| CONFIG_ROOT_BATCH | Not Used | |
| CONFIG_DATA | Not Used | |
| OUTPUT_DATA | Folder used temporarily for Mail Generation and Lifecycle state | <INSTALL_DIRECTORY>/output |
| USER_FILE | File that host JMX Authentication informations | |
| com.salto.console.MAIL_MANAGER_STORE | Type of Storage for Mail Manager | salto.batch.system.MailManagerDBStore (see 1.2.2.9) |
| MAIL_MANAGER_FILE | Used only if Storage is XML | |
| JMX_HTTP_ADAPTOR_PORT | Port of the HTTP JMX adaptor if ACTIVATE_HTTP_ADAPTOR is true | |
| ACTIVATE_HTTP_ADAPTOR | JMX interface that exposes Operations in a Browser (Do not activate in PRODUCTION) | false |
JMX connectivity
This configuration is in file <INSTALL_DIRECTORY>/config/config.properties
This configuration is done by Wizard Installer (see 1.2.2.5)
Configuration parameters:
| Paramter | Description |
| JNDI_NAME | JNDI Name that will appear at the end of the JMX URL |
| JMX_SERVICE_PORT | JMX Port that will appear in the URL (It must be free) |
| NAMING_SERVICE_PORT | Naming service Port
that will appear in the URL (It must be free) |
service:jmx:rmi://<HOST OF THE MACHINE>:<JMX_SERVICE_PORT>/jndi/rmi:// <HOST OF THE MACHINE>:<NAMING_SERVICE_PORT>/<JNDI_NAME>
Database connectivity
This configuration is in file <INSTALL_DIRECTORY>/config/datasource.xml
Mailer connectivity
This configuration is in file <INSTALL_DIRECTORY>/config/mail.xml.
This configuration is done by Wizard Installer (see 1.2.2.9)
Configuration parameters:
| Paramter | Description | Default Value |
| mailHost | Host of the Mail Server | |
| mailPort | Port of the Mail Server | 25 |
| Mailer | Name that will appear in Sent mails |
Logging configuration
This configuration is in file <INSTALL_DIRECTORY>/config/log.properties.
Logging is based on Log4j, and this file controls the Server log level. Batch Logging configuration is hosted in each BAR
See http://logging.apache.org/log4j/docs/manual.html
Cold deployment
How To
This feature enables the (re)deployment at Server Startup of one or more BARs by:
- Putting the bar in folder “<INSTALL_DIRECTORY>\batches-cold-deploy”
- Putting a file called “<BAR_ID>-binding.xml” where BAR_ID is the <display-name > in bar.xml to customize JNDI Mapping (see next paragraph)
JNDI Mapping Customization
If you have to customize the mapping of JNDI resources (Pools), example map jdbc/masterdatas to jdbc/masterdatas_beta, you must put in the folder “<INSTALL_DIRECTORY>\batches-cold-deploy” a file called “<BAR_ID>-binding.xml” where BAR_ID is the <display-name > in bar.xml.
Example:
For STORES where BAR_ID is “STCOM_BATCH”, you will put a file called STCOM_BATCH-binding.xml that contains:
| <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE bar-resources PUBLIC "-//Ubik-Ingenierie //DTD BAR Binding Resource Configuration 1.0//EN" "http://www.ubik-ingenierie.com/consolebatch/config/bar-binding.dtd"> <bar-resources> <bar-resource nameinbar="jdbc/nbo0008" boundname="jdbc/nbo0008" /> <bar-resource nameinbar="jdbc/stcom0024" boundname="jdbc/stcom0024" /> <bar-resource nameinbar="jdbc/stcom0016" boundname="jdbc/stcom0016" /> <bar-resource nameinbar="jdbc/nbo0022" boundname="jdbc/nbo0022" /> <bar-resource nameinbar="jdbc/nbo0015" boundname="jdbc/nbo0015" /> <bar-resource nameinbar="jdbc/nbo0009" boundname="jdbc/nbo0009" /> <bar-resource nameinbar="jdbc/nbo0021" boundname="jdbc/nbo0021" /> <bar-resource nameinbar="jdbc/stcom0014" boundname="jdbc/stcom0014" /> <bar-resource nameinbar="jdbc/stcom0004" boundname="jdbc/stcom0004" /> <bar-resource nameinbar="jdbc/nbo0017" boundname="jdbc/nbo0017" /> <bar-resource nameinbar="jdbc/nbo0016" boundname="jdbc/nbo0016" /> <bar-resource nameinbar="jdbc/nbo0020" boundname="jdbc/nbo0020" /> <bar-resource nameinbar="jdbc/stcom0026" boundname="jdbc/stcom0026" /> <bar-resource nameinbar="jdbc/nbo0018" boundname="jdbc/nbo0018" /> <bar-resource nameinbar="jdbc/stcom0005" boundname="jdbc/stcom0005" /> <bar-resource nameinbar="jdbc/stcom0030" boundname="jdbc/stcom0030" /> <bar-resource nameinbar="jdbc/rangechoice0002" boundname="jdbc/rangechoice0002" /> <bar-resource nameinbar="jdbc/stcom0017" boundname="jdbc/stcom0017" /> <bar-resource nameinbar="jdbc/nbo0023" boundname="jdbc/nbo0023" /> <bar-resource nameinbar="jdbc/nbo0030" boundname="jdbc/nbo0030" /> <bar-resource nameinbar="jdbc/nbo0025" boundname="jdbc/nbo0025" /> <bar-resource nameinbar="jdbc/nbo0014" boundname="jdbc/nbo0014" /> <bar-resource nameinbar="jdbc/nbo0019" boundname="jdbc/nbo0019" /> <bar-resource nameinbar="jdbc/stcom0008" boundname="jdbc/stcom0008" /> <bar-resource nameinbar="jdbc/stcom0027" boundname="jdbc/stcom0027" /> <bar-resource nameinbar="jdbc/stcom0003" boundname="jdbc/stcom0003" /> <bar-resource nameinbar="jdbc/stcom0007" boundname="jdbc/stcom0007" /> <bar-resource nameinbar="jdbc/stcom0010" boundname="jdbc/stcom0010" /> <bar-resource nameinbar="jdbc/stcom0006" boundname="jdbc/stcom0006" /> <bar-resource nameinbar="jdbc/stcom0022" boundname="jdbc/stcom0022" /> <bar-resource nameinbar="jdbc/client" boundname="jdbc/client" /> <bar-resource nameinbar="jdbc/nbo0013" boundname="jdbc/nbo0013" /> <bar-resource nameinbar="jdbc/nbo0029" boundname="jdbc/nbo0029" /> <bar-resource nameinbar="jdbc/nbo0024" boundname="jdbc/nbo0024" /> <bar-resource nameinbar="jdbc/stcom0001" boundname="jdbc/stcom0001" /> <bar-resource nameinbar="jdbc/stcom0023" boundname="jdbc/stcom0023" /> <bar-resource nameinbar="jdbc/rangechoice0005" boundname="jdbc/rangechoice0005" /> <bar-resource nameinbar="jdbc/stcom0028" boundname="jdbc/stcom0028" /> <bar-resource nameinbar="jdbc/stcom0002" boundname="jdbc/stcom0002" /> <bar-resource nameinbar="jdbc/rangechoice0001" boundname="jdbc/rangechoice0001" /> <bar-resource nameinbar="jdbc/rangechoice0015" boundname="jdbc/rangechoice0015" /> <bar-resource nameinbar="jdbc/stcom0013" boundname="jdbc/stcom0013" /> <bar-resource nameinbar="jdbc/cdedir" boundname="jdbc/cdedir" /> <bar-resource nameinbar="jdbc/nbo0010" boundname="jdbc/nbo0010" /> <bar-resource nameinbar="jdbc/stcom0021" boundname="jdbc/stcom0021" /> <bar-resource nameinbar="jdbc/masterdatas" boundname="jdbc/masterdatas_vbeta" /> <bar-resource nameinbar="jdbc/nbo0006" boundname="jdbc/nbo0006" /> <bar-resource nameinbar="jdbc/stcom0011" boundname="jdbc/stcom0011" /> <bar-resource nameinbar="jdbc/nbo0001" boundname="jdbc/nbo0001" /> <bar-resource nameinbar="jdbc/nbo0028" boundname="jdbc/nbo0028" /> <bar-resource nameinbar="jdbc/nbo0003" boundname="jdbc/nbo0003" /> <bar-resource nameinbar="jdbc/stcom0020" boundname="jdbc/stcom0020" /> <bar-resource nameinbar="jdbc/nbo0011" boundname="jdbc/nbo0011" /> <bar-resource nameinbar="jdbc/nbo0026" boundname="jdbc/nbo0026" /> <bar-resource nameinbar="jdbc/stcom0029" boundname="jdbc/stcom0029" /> <bar-resource nameinbar="jdbc/nbo0004" boundname="jdbc/nbo0004" /> <bar-resource nameinbar="jdbc/nbo0005" boundname="jdbc/nbo0005" /> <bar-resource nameinbar="jdbc/stcom0025" boundname="jdbc/stcom0025" /> <bar-resource nameinbar="jdbc/stcom0019" boundname="jdbc/stcom0019" /> <bar-resource nameinbar="jdbc/troc" boundname="jdbc/troc" /> <bar-resource nameinbar="jdbc/nbo0027" boundname="jdbc/nbo0027" /> <bar-resource nameinbar="jdbc/stcom0015" boundname="jdbc/stcom0015" /> <bar-resource nameinbar="jdbc/stcom0018" boundname="jdbc/stcom0018" /> <bar-resource nameinbar="jdbc/nbo0002" boundname="jdbc/nbo0002" /> <bar-resource nameinbar="jdbc/nbo0007" boundname="jdbc/nbo0007" /> <bar-resource nameinbar="jdbc/stcom0012" boundname="jdbc/stcom0012" /> <bar-resource nameinbar="jdbc/nbo0012" boundname="jdbc/nbo0012" /> <bar-resource nameinbar="jdbc/stcom0009" boundname="jdbc/stcom0009" /> </bar-resources> |
What it does
At Startup, the Batch Server will do the following:
- If BAR with another version exists, it will be undeployed
- If file <BAR_ID>-binding.xml exists in batches-cold-deploy folder it will be used
- If file <BAR_ID>-binding.xml does not exist in batches-cold-deploy but exists batches-deploy it will be used
- Otherwise a default binding that maps logical to same physical name will be created
- The BAR will be deployed
- If it succeeds:
- It will appear in deployed BARs on BatchAdmin application
- Success will appear in Deployment History on BatchAdmin application
- If it fails:
- old BAR (if there was one) will be undeployed
- New BAR will not be deployed and moved to batches-deploy-failure and a file called <BAR File Name>.failure will be written that will contains the Failure
- Failure will appear in Deployment History on BatchAdmin application
Batch Administration Webapp:
Create the Database using this script:
- [//nlasrc01/Tetrix/Deploiement/_console/LAST_VERSION/batchadmin/ddl LAST_VERSION\batchadmin\ddl]
Play the following script in the Database of BatchAdmin:
| INSERT INTO parameter(par_context, par_id, par_value, par_description, par_date_upd, par_user_upd, par_date_crt, par_user_crt)
VALUES ('BAR_UPLOAD', 'DIRECTORY', '<PATH TO BAR UPLOAD DIRECTORY>', 'Directory where uploaded BARs in deployment will be stored', SYSDATE, 'PMD', SYSDATE, 'PMD');
VALUES ('CONSOLE_SERVICE', 'IMPLEMENTATION', 'com.ubikingenierie.console.connect.service.JMX', 'Service implementation type', SYSDATE, 'PMD', SYSDATE, 'PMD'); commit; |
Where <PATH TO BAR UPLOAD DIRECTORY> is the path to a Directory where BARs are uploaded before deployment on servers (This is NOT the same one as the Directory used by the BATCH Server)
PERMIT tasks
| PERMIT Task | PERMIT Role | Description |
| MANAGE_CONSOLES | ADMINISTRATOR | Add, Remove,Update a Console connection in the BatchAdmin application and Start/Stop a Server |
| DEPLOY | ADMINISTRATOR | Ability to deploy/undeploy/redeploy a BAR |
| VIEW_DEPLOY | ADMINISTRATOR, SUPERVISOR, GUEST | View Deployment History |
| MANAGE_LOGGING | ADMINISTRATOR, SUPERVISOR | Ability to view loggers, change log levels |
| MANAGE_BATCHES | ADMINISTRATOR, SUPERVISOR | Ability to modify Batches configuration, |
| MANAGE_LAUNCHES | ADMINISTRATOR, SUPERVISOR | Ability to manage Launches configuration, Add/Remove Cron Triggers |
| VIEW_BATCH_ERRORS | ADMINISTRATOR, SUPERVISOR, GUEST | Ability to see Batch Errors and History |
| MANAGE_TRIGGERS | ADMINISTRATOR, SUPERVISOR | Ability to Add/Remove/Modify Cron Triggers |
| MANAGE_LINKERS | ADMINISTRATOR, SUPERVISOR | Ability to see Linkers |
| VIEW_SCHEDULING | ADMINISTRATOR, SUPERVISOR, GUEST | Ability to see Running Batches |
| VIEW_PREVIOUS_EXECUTIONS | ADMINISTRATOR, SUPERVISOR, GUEST | View Previous batches executions |
| VIEW_NEXT_EXECUTIONS | ADMINISTRATOR, SUPERVISOR, GUEST | View Next batches executions |
| MAIL_CONFIGURATION | ADMINISTRATOR, SUPERVISOR | Ability to add/remove Mail recipients |
| DURATION_CONFIGURATION | ADMINISTRATOR, SUPERVISOR | Ability to set max duration limits of a Batch |
| POOL_CONFIGURATION | ADMINISTRATOR | Ability to add/remove/update a Pool |
| POOL_VIEW | ADMINISTRATOR, SUPERVISOR, GUEST | View Pools configuration |
| VIEW_INDICATORS | ADMINISTRATOR, SUPERVISOR, GUEST | View Servers Memory state and pools state |
| VIEW_SYSTEM_PROPERTIES | ADMINISTRATOR | View Server JVM properties |
Deploy the EAR batchadmin-XXX.ear.
Map the pools:
| Logical Name | Physical Pool | Description |
| jdbc/console | jdbc/console | Repository of the Batch Server |
| jdbc/batchadmin | jdbc/batchadmin | Database of the application |
| jdbc/permit | jdbc/permit | PERMIT database |
| jdbc/cbsecurity | No | This pool is not used |
Adding a Batch Server:
You must have the PERMIT task MANAGE_CONSOLES to add a Batch server in the Administration Tool
Open menu Configuration > Manage Consoles
Add a Server
Click on [[Image:]]
Fill this form
[[Image:]]
Where the parameters are:
| Parameter | Description |
| Console ID | The Console ID that identifies uniquely the Batch Server in DB (see 1.2.2.4) |
| JMX URL | The JMX URL that was generated in <INSTALL_DIRECTORY>/config/jmx-service-url.txt (see 1.2.5.3) |
| JMX User | The JMX login |
| JMX Password | The JMX password |
| File Transfer Host | The Host where the Batch Server is running |
| File Transfer Port | The Port of the Embedded BAR Server (see 1.2.2.7) |
| Console Pool | The JDBC Pool to the Batch Server repository of the configured Batch Server |
| Comments | A Comment that will appear when you hover over a link |
Finish the Step
Click on [[Image:]]
