deleteBPMCompatEndpoints command
Traditional:
Use the deleteBPMCompatEndpoints command
to delete unused compatibility Business Automation Workflow endpoint objects that were required for compatibility with deprecated WebSphere® Lombardi Edition scenarios. The compatibility endpoint objects include the LSW_SERVLET, EXPOSED_ITEMS, TASK_REST_API, and TASK_TEMPLATE_REST_API objects, which can refer to virtual hosts.
The deleteBPMCompatEndpoints command is run using the AdminTask object of the wsadmin scripting client.
Prerequisites
The following conditions must be met:
- In a network deployment environment, run the command on the deployment manager node. In a single-server environment, run the command on the stand-alone server.
- If the deployment manager or stand-alone server is stopped, use
the
wsadmin -conntype noneoption to run the command in disconnected mode (which is the recommended mode for this command). - If the deployment manager or stand-alone server is running, you must connect with a user ID that has WebSphere Application Server configurator privileges. Do not use the
wsadmin -conntype noneoption.
Location
Start the wsadmin scripting client from the profile_root/bin directory. The deleteBPMCompatEndpoints command does not write to a log file, but the wsadmin scripting client always writes a profile_root/logs/wsadmin.traceout log file where you will find exception stack traces and other information.
Syntax
deleteBPMCompatEndpoints
[-de deployment_environment_name]Parameters
- -de deployment_environment_name
- A parameter that specifies the name of the current deployment environment. If there is only one deployment environment in the WebSphere cell, you can omit this parameter.
Examples
wsadmin -conntype none -lang jython
wsadmin>AdminTask.deleteBPMCompatEndpoints(['-de', 'De1'])
wsadmin>AdminConfig.save()