Deploying custom webcenter portal application (EAR) file on 11.1.1.8 webcenter domain

[Chetan Paul]

Hi,

We are developing a custom webcenter portal application (11.1.1.8.3 webcenter). This custom portal also includes custom ADF task flows (as shared ADF libraries jar files bundled in the application EAR file).

We are deploying this application to a domain with an admin server and 2 managed servers cluster (wc_custom_portal1 and wc_custom_portal_server2). These custom webcenter portal managed servers are created as per Oracle's documentation by extending the webcenter domain with the custom portal template. The MDS repository is also setup and registered for the webcenter managed server cluster. The domain is running in "Production Mode"

We are building the EAR file in JDEVELOPER 11.1.1.7 and using the Enterprise Manager console to deploy the EAR file. The deployment completes perfectly fine (without any errors/warnings). But when we access the custom portal application, the latest changes deployed are not reflected until the domain is restarted (i.e. both managed servers are restarted after EAR deployment).

Shouldn't the latest deployment be automatically picked and served, without the need to restart managed servers? Can you please suggest if we missing something basic?

Appreciate your response and help.

PS: We have been following this forum for the past 3+ years and we are a big fan of this forum and appreciate all the contributors for insights into issues and prompt solutions as well as share their real project experiences.

Thanks

Chetan Paul

[Bat Gmail]

I primarily use Webcenter portal so not not sure if this is the best practice for custom Webcenter but this is one flow I have seen deploying it without restarting the managed servers.

1. Via Enterprise Manager

2. Undeploy the application and

3. Deploy the new .ear application deployed from JDev.

Make sure you have the new version updated in the build ear (meta-inf)

Note: one issue have seen with approach was the runtime customizations were getting removed and hence a new metadata partition was specified during the deployment.

Thanks,

Arun

--
--
You received this message because you are subscribed to the WebCenter Enterprise Methodology Group (http://groups.google.com/group/webcenter-emg). To unsubscribe send email to webcenter-em...@googlegroups.com
 
All content to the WebCenter EMG lies under the Creative Commons Attribution 3.0 Unported License (http://creativecommons.org/licenses/by/3.0/). Any content sourced must be attributed back to the WebCenter EMG with a link to the Google Group (http://groups.google.com/group/webcenter-emg).

---
You received this message because you are subscribed to the Google Groups "WebCenter EMG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webcenter-em...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chetan Paul]

Thanks Arun,

I am going to try out the below steps with a new version updated in the META-INF.

I will share the results.

Chetan Paul