EMC Documentum - xCP 2.x Updating Java Services
1 like1,718 views
The document discusses two methods for updating Java services in EMC xCP: 1) updating the Java service artifact in xCP Designer and redeploying, which requires additional steps in xCP Designer 2.1, or 2) updating the JAR file directly in the repository. It provides detailed steps for each method.
EMC Documentum - xCP 2.x Updating Java Services
- 1. 1© Copyright 2015 EMC Corporation. Allrights reserved. Updating Java Services EMCENTERPRISE CONTENT DIVISION Michael Phipps 30 November 2015
- 2. 2© Copyright 2015 EMC Corporation. Allrights reserved. What is a Java Service Java Services are used to execute custom Java code within a Process Stored in the docbase as a dmc_module (with dmc_jar) files. Downloaded to local DFC instance to execute (on the webapp for a Stateless Process, or to the JMS for a Stateful Process).
- 3. 3© Copyright 2015 EMC Corporation. Allrights reserved. Creating in Designer Java Service Artifact is created in xCP Designer. Once you’ve selected your JAR file, it will be added to the underlying Application folder structure – ie. Applicationsdemo_appdemo_applibxxxx.jar Development Changes may be required – ie. you may need to update the JAR file with new / altered code.
- 4. 4© Copyright 2015 EMC Corporation. Allrights reserved. Methods for Updating a Java Service Two Options for updatingthe Java Service: Update the Java Service artifact in xCP Designer, then redeploy – Slightly different step required in 2.1 and 2.2 Update the dmc_jar object in the repository directly
- 5. 5© Copyright 2015 EMC Corporation. Allrights reserved. Updating the Java Service in xCP Designer 2.2 1. Open the Java Service in xCP Designer. In the Shared Java Services Libraries, select your new JAR from the file system. The above steps are not sufficient to have the new JAR deployed. The JAR will be updated in the application structure, however the change does not update anything in the Java Service artifact. As the artifact shows as unchanged, during the next incremental deployment, it will be skipped. So, we need to perform additional action to trigger a refresh of the Artifact. 2. Make a minor update the artifact (for example, adding something in the Java Service’s description field) – this will result in the new JAR being deployed. **A Full / Clean xMS deployment would also update the JAR
- 6. 6© Copyright 2015 EMC Corporation. Allrights reserved. Updating the Java Service in xCP Designer 2.1 – additional step Same as 2.2, however when updating the description of the Java Artifact, you may receive an error: Due to a known defect, which is fixed in 2.2. Occurs if the system name of the artifact contains both upper and lower case characters. After reloading xCP Designer, the artifact filename is changed to all lowercase – this makes it out of sync, which causes the above error
- 7. 7© Copyright 2015 EMC Corporation. Allrights reserved. Updating the Java Service in xCP Designer 2.1 – additional step 1. Close xCP Designer 2. Navigateto<Designer Home> Applications<app><app>ArtifactsJava 3. Edit your xxxxx.javaservice file with Notepad. 4. In the name value, set this to be identical to the name of the artifact– ie. remove the capital letters 5. Navigateto<Designer Home> Applications<app><app> 6. Delete the .index file 7. Restart Designer – you should now be able to add a comment to your Java Service – this will allow you to redeploy with the new JAR deployed **A Full / Clean xMS deployment would also update the JAR
- 8. 8© Copyright 2015 EMC Corporation. Allrights reserved. Updating the JAR file in the Repository Can be used during Development as a quicker way to test code changes. Cannot change the Inputs / Outputs of the method – these are mapped in xCP Designer, so will fail if these are altered Class still needs to be added to xCP Designer so it can be correctly packaged – ie. to build and move to another environment.
- 9. 9© Copyright 2015 EMC Corporation. Allrights reserved. Updating the JAR file in the Repository - Steps In DA: 1. Navigate to System/Modules/<xcp workspace>/<your java service/ 2. Checkout the JAR file 3. Check In and select the new JAR file