Deploying a Customized Contentspace (Deprecated)

After you have completed modifying the files for your customization, you redeploy the LiveCycle Content Services (deprecated) EAR, which contains the files you modified to customize the LiveCycle Contentspace (Deprecated) user interface.

Remarque : Adobe is migrating Adobe® LiveCycle® Content Services ES customers to the Content Repository built on the modern, modular CRX architecture, acquired during the Adobe acquisition of Day Software. The Content Repository is provided with LiveCycle Foundation and is available as of the LiveCycle ES4 release.

    Summary of steps

    Complete these steps to deploy a customized version of Contentspace.

    1. Repackage the EAR file. (See Repackaging the EAR file.)

    2. Deploy the EAR file. (See Deploying the EAR file.)

    3. Test and verify the changes. (See Testing customizations.)

    Repackaging the EAR file

    After you have completed your customizations, you must rebuild the WAR and EAR file. This procedure presumes that you have created a folder structure necessary to modify the contents of the contentservices.war file from the adobe-contentservices.ear file and for correctly rebuilding the adobe-contentservices.ear file. (See Creating a development environment.)

    To repackage the EAR file:

    1. In the folder, such as CustWorking, where you made your modifications to the extracted contents of the contentservices.war file, recreate the WAR file by using an archiving utility. The name of the WAR file must be contentservices.war.

      For example, in the command prompt, type the following command:

              jar.exe -cvfm contentservices.war META-INF\MANIFEST.MF *

    2. Copy the contentservices.war file that you created in the previous step to the folder for rebuilding the EAR file, such as CustBuildEAR.

    3. Go to the folder that you copied the contentservices.war file to in the previous step, and re-create the EAR file by using an archiving utility. For example, in the command prompt, type the following command:

              jar.exe -cvfm adobe-contentservices.ear META-INF\MANIFEST.MF *

    Deploying the EAR file

    After you compile the localization file, you can deploy it to the LiveCycle server for testing.

    Important : Before you deploy your customized adobe-contentservices.ear file, it is recommended that you create a backup copy of the original adobe-contentservices.ear file.

    To deploy the EAR file:

    1. Back up the original adobe-contentservices.ear file to another location.

      Remarque : Do not back up the adobe-contentservices.ear file in the same folder as your deploy folder.

    2. Undeploy the adobe-contentservices.ear file from your application server. Depending on the application server you use, you may need to stop the application server first. If you customized the files on a separate computer, you may need to copy your custom adobe-contentservices.ear file to the computer where LiveCycle is installed.

      For example, for a JBoss Turnkey installation of LiveCycle, stop the JBoss application server to undeploy all deployed EAR files.

    3. Deploy the new adobe-contentservices.ear file to the application server. The procedure varies depending on the application server you are using.

      For example, for a JBoss Turnkey installation, you copy the adobe-contentservices.ear.ear file to the [install_dir]/jboss/server/all/deploy folder where [install_dir] is the location where you installed LiveCycle.

    4. Restart the application server to restart LiveCycle. Restarting the application server deploys your new adobe-contentservices.ear file.

    Testing customizations

    You can verify that your EAR file deployed by looking at the server logs. For example in a JBoss turnkey installation, you can view the server.log file located at [install_dir]/jboss/server/all/log where [install_dir] represents the location where LiveCycle was installed.

    You test your customization by typing http://[servername]:[port]/contentspace in a web browser and logging in to Contentspace, where [servername] is the name of the server where LiveCycle is installed and [port] is the port number to access LiveCycle.

    Remarque : You may need to refresh your web browser’s cache to see your changes. Many web browsers cache CSS files and images.

    The following are recommended testing considerations for verifying a customized LiveCycle Contentspace:

    • Verify that any images you changed appear properly and are sized appropriately for the component.

    • Verify that images blend in with the background color you selected to give a consistent appearance.

    • When modifying colors, verify that their appearance is consistent and text and images are visible. Sometimes the colors you choose may inadvertently be the same.

    • In cases where different sizes of the same image are required, verify that the image appears correctly in both circumstances.

    • For fonts, verify that they appear correctly and do not overlap or cross boundaries.