1. A managed resource can be deleted through the OpenEdge Console
when it is not running.
If the resource is currently running the DELETE button will not be available.
For example
- A Database or Ubroker resource will not show the DELETE button in the OpenEdge Console page if that managed resource is currently running.
- The Delete button will only appear if the Java Servlet Engine (e.g. Tomcat) which is hosting the WSA instance is offline.
To remove the entry from OEM use the OpenEdge Explorer interface.
Within the resource, click on the DELETE button. After successful deletion the related .properties file and configuration database will be updated.
- In versions prior to 11.3 the database in $OEMGMT/config
- In OpenEdge 11.3 or later the database is in $OEMGMT/config/configdb
For example:
To delete a WebSpeed instance:
- Select Resources in the management console menu bar. The main resource types appear in the list frame.
- In the list frame, browse to and select the WebSpeed instance to delete (eg wsbroker1). The Details page for that instance appears in the detail frame.
- Select Delete, and then click OK to confirm the deletion.
2. Manually deleting managed resources in the conmgr.properties / ubroker.properties file will not remove them from the configuration database.
The next action is then to delete the resource in the OpenEdge Console.
Example: The asbroker1 configuration is deleted while the AdminServer is running
APPSERVER: ASBROKER1
ALERTS: WarmStartFinished
Delete Resource
The AdminServer configuration definition for this AppServer resource no longer exists
Choose delete to permanently remove this AppServer resource If the entry was removed from the conmgr.properties or ubroker.properties and re-added to the conmgr.properties or ubroker.properties it may cause the AdminServer to error because a duplicate entry is being attempted. The OpenEdge Manager stores resources that are discovered or created in its own configuration database:
- Entries added to the conmgr.properties or ubroker.properties will create entries in the OEM database.
- Removing entries from the conmgr.properties or ubroker.properties does not remove them from the OEM database.
Article
Programmatically creating entries in conmgr.properties without correctly deleting them from AdminServer causes errors. 3. Another method of deleting resources is to use
MERGEPROP -action delete. The AdminServer will find that the resource in the configdb is no longer there and will Alert to this fact. The next action is then to delete the resource in the OpenEdge Console as described above. For further information refer to Articles:
