Creates or updates EIS Entries defined within properties files. The EIS entry applications will be updated at the end.
| Tip | ||
|---|---|---|
| ||
This operation will Update Adapter after updating processing EIS Entries. To only Save Adapter Plan, use the generateEISDeploymentPlans operation instead of this operation. To Redeploy Adapter instead, use the createOrUpdateEISEntriesupdateEISDeploymentPlans1361052319operation 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. |
...
If deploying to a cluster that does not make use of shared storage, this operation will fail to complete if any of the configured adapters have never been deployed previously. See the generateEISDeploymentPlans operation for information on using multiple plugin operations to create the deployment plans, sync them to all the servers, and then complete the redeployment of the adapter so that they take effect.
Blog Posts
Environment/Instance Properties
...
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| Properties File Path | FILE_PATH_TO_PROPERTIES | No | Comma-separated list of paths to the properties file(s). |
Outputs
Output Name | Required | Description |
|---|---|---|
FDWLS_OUT_IS_RESTART_REQUIRED | 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) |
...