| Oracle Agile Engineering Data Management Batch Client for Agile Release e6.2.1.0 E69110-01 |
|
 Previous |
 Next |
| Oracle Agile Engineering Data Management Batch Client for Agile Release e6.2.1.0 E69110-01 |
|
Previous |
Next |
This chapter describes the several settings related to the Java Wrapper framework of the Agile e6.2.1.0 Batch Client in the Scenario mode and ECI mode.
The Agile e6.2.1.0 Batch Client uses the Java Wrapper as its run-time frame work.
The Java Wrapper needs a configuration file:
<installdir>\axalant\ini\batch_simple_wrapper.conf
The Java Wrapper supports the following shutdown mode:
Simple type:
The Java application, controlled by the Java Wrapper, will be configured and simply killed at shutdown. This mode is used for the Java Daemon
Here is a short description of the settings which may be adapted to implement a custom batch solution.
This section in the configuration defines the controlled Java application and its command line parameters.
# Application parameters. Add parameters as needed starting from 1. wrapper.app.parameter.1=com.agile.testclient.BatchClientApp wrapper.app.parameter.2=-p%EP_ROOT%/examples/LgvLoop.properties wrapper.app.parameter.3=-i%EP_ROOT%/examples/LgvLoop.groovy wrapper.app.parameter.4=-T%EP_ROOT%/axalant/ini/testclient.properties
This section within the configuration file defines the MS Windows Service settings. Here, the name of the server can be defined and some extended settings for services.
#**************************************************************** # Wrapper NT Service Properties #**************************************************************** # WARNING - Do not modify any of these properties when an application using this configuration file has been installed as a service. # Please uninstall the service before modifying this section. The service can then be reinstalled. # Name of the service wrapper.ntservice.name=AgilePLM_Batch_Service # Display name of the service wrapper.ntservice.displayname=AgilePLM_Batch_Service # Description of the service wrapper.ntservice.description=Batch Service for Agile PLM # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1= # Mode in which the service is installed. AUTO_START or DEMAND_START wrapper.ntservice.starttype=AUTO_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=false
The used Agile e6.2.1.0 Batch Client scenario and the corresponding property file are defined as command line parameters in the Java Wrapper configuration file as you can see above.
This configuration file has to be adapted to your environment.
|
Note: The Batch Client bundle provides an example (located in directory C:\Program Files\Agile_e6\batchclient\examples) which has to be adapted to your environment. |
| host=<PLM host> | Hostname of the Agile e6 server |
| port=<PLM port> | Port number of the Java Daemon |
| env=<PLM env> | Application name to connect to |
| url=<PLM-API URL> | Defines the URL for the HTTP Proxy of the Agile e6 server. If you want to use the URL, you need to uncomment the line in the configuration file.
Example: url=http://plm.example.com:7101/plm-api-axis/services |
| encoding=UTF-8 | Default encoding for the ECI connection |
| scope=BATCH | Scope for the Java Daemon. This should always be BATCH for batch applications |
| varenv.EP_DDM_SITE | The DDM Site |
| url | The PLM-API URL. If connection to e6 should be made via PLM-API the HTTPS URL of the PLM-API must be used. The Weblogic server must also be configured to use HTTPS. For more information, see the Architecture Guide, Administration Guide and the Online Help. |
| varenv.ep_root=<install dir>/Agile_e6/BatchClient
varenv.axalant_root=<install dir>/Agile_e6/BatchClient/axalant |
Directories |
| varenv.EP_MACH=<client ep_mach> | Platform |
| Security.KeyStoreFile=file://<install dir>/Agile_e6/BatchClient/init/wallet/private/batch/cwallet.sso
Security.KeyAlias=orakey |
Security settings |
| client1=<PLM user>,<PLM password>,com.agile.EciServer | PLM Client |
| varenv.EciServer.StartupImmediately=true | |
| varenv.EciServer.ConnectionDelay=100 | Delay between two incoming ECI connection requests in milliseconds |
| varenv.EP_DDM_SITE=<DDM site> | Sets the DFM site for the Batch Client. |
| varenv.HTTP_FMS_MODE=false | Defines if the HTTP FMS Client or the native FMS Client must be used.
Possible values: true / false |
The security setting needs to be adapted in the Batch Client properties. The SecurityKeyStoryFile has to point to the Oracle wallet of the Batch Client installation.
In the next section you can find instructions on how to create an Oracle wallet for your batch client installation.
Example Windows:
Security.KeyStoreFile=file://C:/Program Files/Agile_e6/BatchClient/init/wallet/private/batch/cwallet.sso
Example UNIX:
Security.KeyStoreFile=file:///app/plm/BatchClient/init/wallet/private/batch/cwallet.sso
|
Note: The Batch mode can be set in the property files LGVCall.properties, LgvLoop.properties, OfsPdf.properties, and vuelink.properties.The eciserver mode should always be BATCH. When no mode is set in the property files, the default value is BATCH. |
The User credentials are stored in the Agile e6.2.1.0 Batch Client properties file.
The Batch Client installation needs to create a new installation specific Oracle wallet which needs to be protected against unauthorized file access. For more information refer to the Agile EDM Security Guide Chapter Wallets > Batch Client.
|
Note: The "old" batch solution of the EDM server is still available, but due to security risks this solution is not recommended. |
To enable the EDB_BATCH mechanism, the security level has to be decreased to unrestricted.
The security level can be configured in the <environment>.xml file located in the <ep_root>/init directory.
Example:
<IPC AbsEciUrl="eci://localhost:19997" SecurityLevel="unrestricted" TicketTimeout="600"> </IPC>
|
Note: The security level setting also controls the security settings of the ECI connection. A client needs no authentication to connect to an unrestricted ECI server. Please ensure that this setting is not effective for EDM servers, which allow to be contacted via ECI. |
The standard Agile e6.2.1.0 Batch Client bundle is pre-configured for executing a LogiView Start/Stop scenario and cannot be used out of the box for a starting a simple LogiView scenario. Especially the wrapper configuration file needs a different wrapper Java MainClass and different wrapper application parameters.
The Agile e6.2.1.0 Batch Client requires the following configuration files / start scripts:
|
Note: the following files / start scripts can all be renamed! |
<ep_root>\axalant\ini\batch_wrapper.conf <ep_root>\axalant\ini\testclient.properties <ep_root>\examples\LGVCall.properties <ep_root>\examples\LGVCall.groovy <ep_root>\axalant\cmd\batchclient.cmd (Windows) <ep_root>/axalant/scripts/batchclient (Unix)
To enable the Batch Client for executing a simple LogiView procedure, the Agile e6.2.1.0 Batch Client bundle is delivered with pre-configured examples which call a simple LogiView (LGV) procedure. The example files are located in the installation folder as follows:
| Batch command script | axalant/cmd/Simple.cmd |
|---|---|
| Wrapper configuration | axalant/ini/batch_simple_wrapper.conf |
| Batch scenario | axalant/examples/LGVCall.groovy |
| Batch configuration | axalant/examples/LGVCall.properties |
