Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Custom Livecycle WorkSpace Deploying issue

Avatar

Level 2

Can some one help me in deploying the custom workspace EAR file having name other than myCustomApplication.ear

I am able to deploy the ear file with the default name myCustomApplication as mentioned in customize_workspace_es2sp1.pdf

While creating a same build in the same manner with the other name dont work out for me.

Will be thankful for your responses.

-Ronak

1 Accepted Solution

Avatar

Correct answer by
Level 3

Hi Ronak,

You must change the application.name in your build.xml found the workspace-ui project as Diana mentions. In addition, I assume you want to change the URL that your EAR is deployed to?

If so, you need to change the web.xml file found in the templates folder in the workspace-ui project. In addition, in the LiveCycle Administration Console, you must register the new URL in the config.xml file. Instructions for both are found here on pages 29 and 35 respectively. Hope that helps!

...Gil

View solution in original post

0 Replies

Avatar

Level 4

Hi Ronak

I assume you set the "application.name" property in the build.xml file for the workspace-ui project and then built the project?

What appserver are you using?

What error are you seeing in the appserver log on deploy?

Diana

Avatar

Correct answer by
Level 3

Hi Ronak,

You must change the application.name in your build.xml found the workspace-ui project as Diana mentions. In addition, I assume you want to change the URL that your EAR is deployed to?

If so, you need to change the web.xml file found in the templates folder in the workspace-ui project. In addition, in the LiveCycle Administration Console, you must register the new URL in the config.xml file. Instructions for both are found here on pages 29 and 35 respectively. Hope that helps!

...Gil

Avatar

Level 2

Thanks gil and Diana.

The issue was with the web.xml.


It worked out for me.

-Ronak