Creates or updates EIS Entries defined within properties files. The EIS entries will be redeployed at the end.
The properties files will be processed for property replacement using ${{VARIABLE_NAME}} format. See Property Replacement Support for more information about property replacement.
| Tip |
|---|
Adapter DeploymentThis operation will Redeploy Adapter at the end after processing EIS entries. To only Save Adapter Plan, use the generateEISDeploymentPlans operation instead of this operation. To Update Adapter instead, use the updateEISDeploymentPlans operation instead of this operation. So, if you want save or update the Adapter, then create a workflow containing the desired EIS operation. If you want to process JMS, DataSource, and Work Manager entries in same workflow add those necessary operations in the same workflow. |
...
Property Name | Property Code | Required | Description |
|---|---|---|---|
Properties File Path |
| No | Comma-separated list of paths to the properties file(s). |
Outputs
Output Name | Required | Description |
|---|---|---|
| No | A boolean value that indicates whether the server needs to be restarted to finish applying the configuration changes. You could use this in a workflow condition. |
...
Each EIS Entry must contain the following required properties
Property Name | Description |
|---|---|
Adapter | The adapter name (e.g. JmsAdapter, DbAdapter). The adapter name is used to find its associated rar file, so it must be named exactly the same. The first part of the adapter name will also be used to create the plan file name. |
JNDI | The JNDI name (e.g. eis/db/SOA) |
...