Deploying JSP files to Weblogic server

Hi,

Iam working on TS 6.5 SP-3 on Solaris 9. In our project we have a requirement to generate JSP pages using PTs and deploy these JSPs through OD to a weblogic application server (WL 9.2 on Sol-9). We also develop static JSPs and java classes which has business logic and maintain this code in CVS. Anthill pulls the java code from CVS repository and deploy to application server as an .ear file.

.ear has both static and dynamic content , static content is pushed from CVS repository and dynamic content should be pushed from Teamsite. We are facing difficulty in configuring the Opendeploy target path for deploying the dynamic JSPs as we don't have a physical location on the target server to deploy.

One way i can think of is exploding the ear file so that i get a physical location in the weblogic server for OD to deploy the dynamic JSP files. Is there any efficient way to handle this scenario?

Have you handled this scenario before? Any pointers?

Thanks,
Arun.

Find more posts tagged with

Comments

Migrateduser

When you mean deploy the dynamic JSPs to the weblogic server, are you talking about making it part of the EAR file? If thats the case, then you might have to run some DnR script to unjar the EAR, add these JSP's and then again jar the EAR file.

We have something similar, but most of the steps happen before we build the ear. What we do is, assemble all the necessary files on the teamsite server both from VSS & teamsite in the required structure and then bundle (using ant) and deploy the ear (using OD).

ISCBorisB

Hi,

Iam working on TS 6.5 SP-3 on Solaris 9. In our project we have a requirement to generate JSP pages using PTs and deploy these JSPs through OD to a weblogic application server (WL 9.2 on Sol-9). We also develop static JSPs and java classes which has business logic and maintain this code in CVS. Anthill pulls the java code from CVS repository and deploy to application server as an .ear file.

.ear has both static and dynamic content , static content is pushed from CVS repository and dynamic content should be pushed from Teamsite. We are facing difficulty in configuring the Opendeploy target path for deploying the dynamic JSPs as we don't have a physical location on the target server to deploy.

One way i can think of is exploding the ear file so that i get a physical location in the weblogic server for OD to deploy the dynamic JSP files. Is there any efficient way to handle this scenario?

Have you handled this scenario before? Any pointers?

Thanks,
Arun.

We do not know nearly enough about the project to provide any non-trivial advise.

Normally CMS Deployments and EAR Deployments have very different asynchronous schedules. EAR (Code) gets promoted relatively
less often, normally upon QA/UAT approval. CMS Components may go live several times a day, approval cycle includes something
like Business/Legal approvals, often promoted through Workflows.

In general if you have some Application Environment with various assets' sources it pays to design a dedicated destination
per Source, even for the identical MIME Types, (like *Code JSPs* and *CMS JSPs*). That allows you to create proper Source Base
Lines, reduce Deployment dependencies, have correct CVS/CMS branching etc. Other than that - you'll need to talk to
your architect and compare pro's and con's of various Deployment scenarios