The need to clean up an install of Adobe LiveCycle on IBM WebSphere occurs at various times during an application’s development life cycle. Steps to achieve this are provided here. The interface is the WebSphere Admin Console, usually available via HTTP on port 9060 by default.
LiveCycle touches various parts of the J2EE feature set, including JMS, JDBC, and J2C. Even if you don’t intend to clean up an install, this provides an outline of the various parts of WebSphere that LiveCycle touches.
Undeploy the EAR files
Three EAR files are usually involved. Since system administrators are free to name them whatever they want, likely names would include terms such as LiveCycle, LiveCycle Native, LiveCycle Workspace. In addition, depending on the LiveCycle features you have licensed, there could also additional EARs to un-deploy like Content Services, and Lava. Also, if LiveCycle was configured using LiveCycle Configuration Manager (LCM), there will be an additional EAR file called ‘adobe-lcm-lcvalidator‘ that need to be undeployed.
Service Integration Bus (SIB)
LiveCycle requires a Service Integration Bus. Navigate to Service Integration->Buses and delete the bus that was defined for LiveCucle. It is named “IDP_JMS_Bus“.
Navigate to Resources->JMS->Queue connection factories. Delete two queue connection factories, namely ‘JobManagerQueueConnectionFactory‘ and ‘QueueConnectionFactory‘.
Navigate to Resources->JMS->Topic connection factories. Delete the topic connection factory named ‘TopicConnectionFactory‘.
LiveCycle uses four queues for JMS point-to-point messaging. Navigate to Resources->JMS->Queues. Make sure the scope is set to ‘All scopes’. Delete the queues ‘adobe_JobManagerQueue‘, ‘adobe_PECommandQueue‘, ‘adobe_PEDCommandQueue‘ and ‘adobe_PEInteractionQueue‘.
LiveCycle uses one topic for JMS publish-subscribe (pub-sub) messaging. Navigate to Resources->JMS->Topics. Make sure the scope is set to ‘All scopes’. Delete the topic ‘adobe_TaskEventTopic‘.
LiveCycle uses four activation specifications for its queues and topics. Navigate to Resources->JMS->Activation specifications. Make sure the scope is set to ‘All scopes’. Delete the activation specifications named ‘JobManager_AS‘, ‘PECommand_AS‘, ‘PEDCommand_AS‘ and ‘Task_Event_AS‘.
Deleting the Service Integration Bus will delete the Queue Destinations defined for LiveCycle. For the record, these queue destinations are named ‘adobe_JobManagerQueue‘, ‘adobe_PECommandQueue‘, ‘adobe_PEDCommandQueue‘ and ‘adobe_PEInteractionQueue‘. To see them listed, navigate to Service Integration->Buses->IDP_JMS_Bus->Destinations.
Deleting the Service Integration Bus will delete the single Topic Destination defined for LiveCycle. For the record, this topic destination is named ‘adobe_TaskEventTopic‘. To see it listed, navigate to Service Integration->Buses->IDP_JMS_Bus->Destinations.
Navigate to Resources->JDBC->JDBC Providers. Make sure the scope is set to ‘All scopes’. Delete the JDBC Providers (usually three) defined for LiveCycle. They will have names that include terms like IDP_DS, EDC_DS and JMS_DS.
JDBC Data Sources
Deleting the JDBC Provider usually deletes the Dtaa Sources defined using that Provider. However, if you would like to keep the JDBC Provider, you can delete the Data Sources. Navigate to Resources->JDBC->Data Sources. Make sure the scope is set to ‘All scopes’. Delete the Data Sources (usually three) defined for LiveCycle. They will have names that include terms like IDP_DS, EDC_DS and JMS_DS.
LiveCycle requires a data replication domain to be defined for HTTP session replication amongst members of a cluster. Navigate to Environment->Replication Domains. Delete the data replication domain defined for LiveCycle (LCM would have named it “livecycle“).
J2C Authentication Alias
In the WebSphere Admin Console, navigate to Security->Secure administration, applications, and infrastructure->Java Authentication and Authorization Service->J2C authentication data and delete all (usually three) entries for LIveCycle database access. Names can include terms such as IDP_DS, EDC_DS and JMS_DS.
If a virtual host has been defined exclusively for LiveCycle, delete it.
On each node in the cluster, navigate to $WAS_INSTALL_ROOT/profiles/your_WAS_profile_name/tranlog/your_WAS_cell_name/your_WAS_node_name/your_WAS_server_name/transaction/ and delete everything below it.
If you had defined any SSL repertoires exclusively for LiveCycle, delete them.
If you decide to delete the two clusters created for LIveCycle, also remember to delete the corresponding log folders for the member servers on each of the nodes.
Also, remember to drop the tables, views and sequences on the database side, whether it be IBM DB2, Oracle, or Microsoft SQL Server.
Re-start the LiveCycle cluster as well as the LIveCycle JMS cluster afterwards.