nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Publish Live Site Content WF - Deploy Configuration

iwTech

We trying to configure the OOTB “Publish LiveSite Content.ipm”
& “Configurable_Default_Submit.ipm” (using WFM)
Please guide me where should I Configure Source and Destination path
for OD deployment

Thanks
Vin

Find more posts tagged with

Comments

Faizi

Hi
We trying to configure the OOTB “Publish LiveSite Content.ipm”
& “Configurable_Default_Submit.ipm” (using WFM)
Please guide me where should I Configure Source and Destination path
for OD deployment

Thanks
Vin

All the Destination path (target directories) of deployment should be defined in

odbase.xml

file and Deployment node (deployment server) should be define in odnodes.xml file.
For "

Publish LiveSite Content Workflow

" define the Livesite runtime path in

odbase.xml

, like below:
[HTML]

................................
................................

[/HTML]
For "

Configurable_Default_Submit"

workflow pass a deployment configuration file in Deploy Task variable odDeploymentName. Deployment configuration file should be kept at

od-home/conf

location. The are defined for target that should be added in

odbase.xml

file in allowedDirectores node.
For further detail go through the WFM User Guide.
Hope this helps.

page2.png

page1.png

Hi
We trying to configure the OOTB “Publish LiveSite Content.ipm”
& “Configurable_Default_Submit.ipm” (using WFM)
Please guide me where should I Configure Source and Destination path
for OD deployment

Thanks
Vin

can "Publish LiveSite Content.ipm" be used for OD deployment?

Faizi

can "Publish LiveSite Content.ipm" be used for OD deployment?

It is already doing OD as well as DD deployment. What do you want to do please elaborate in detail.

ericzz

It is already doing OD as well as DD deployment. What do you want to do please elaborate in detail.

I want to use "Publish LiveSite Content" workflow to do OD deployment for certain files to publish these files from CMS to our application server(not livesite runtime). could you please tell me how to implement it? Thanks.

Faizi

I want to use "Publish LiveSite Content" workflow to do OD deployment for certain files to publish these files from CMS to our application server(not livesite runtime). could you please tell me how to implement it? Thanks.

You need to customize the

Publish Livesite Content

workflow. In this workflow deployment performed by

URL Task

. For file system deployment replace this task by

Deploy Task

and pass the deployment configuration file name with variable

odDeploymentName

only, rest of the name value pair variables are optional. Deployment config file should be located at

od-home/conf

folder.
Hope this helps.

ericzz

You need to customize the
Publish Livesite Content
workflow. In this workflow deployment performed by
URL Task
. For file system deployment replace this task by
Deploy Task
and pass the deployment configuration file name with variable
odDeploymentName
only, rest of the name value pair variables are optional. Deployment config file should be located at
od-home/conf
folder.
Hope this helps.

But you said we can do OD deployment with "Publish Livesite Content" workflow. So, is it neccessary to customize it if we only deploy simply?

Faizi

But you said we can do OD deployment with "Publish Livesite Content" workflow. So, is it neccessary to customize it if we only deploy simply?

Yes it is necessary to customize the "Publish LiveSite Content" workflow to perform normal (file system) deployment.

ericzz

Yes it is necessary to customize the "Publish LiveSite Content" workflow to perform normal (file system) deployment.

Why? I found "Publish LiveSite Content" workflow can default deploy files to livesite runtime which are installed on application server, so I guess there is some configuration we can update to change the target server.

listbox.rptdesign

Faizi

Why? I found "Publish LiveSite Content" workflow can default deploy files to livesite runtime which are installed on application server, so I guess there is some configuration we can update to change the target server.

You are correct. It performs same but you do not know how it is performing this.
URL Task (Production Deployment) is calling a java bean id that is internally mapped with Livesite Deployment configuration file "

OpenDeployWebRoot.xml

" that is located at

od-home/conf/LiveSite

folder. This file is used through out the any Livesite runtime production deployment. There are also many Metadata postfix naming files that is used for Data Deployment.
These files are static defined in configuration file for java bean. To replace these files (or any) with other deployment configuration file you have to customize

livesite_customer

and rebuild the application.
One thing more can possible but i discourage it. Becuase it will badly effect the Livesite Runtime deployment.
So it is better to customize the OOTB workflow and replace with Deploy Task and save with other name instead of ultering existing.
Hope I make you understand.

NewspaperStyleReportWithGrouping.rptdesign

Adam Stoller

Yes it is necessary to customize the "Publish LiveSite Content" workflow to perform normal (file system) deployment.

A better suggestion would be to copy-and-modify the existing WFM so that your custom copy has the changes in it. Whether you want to change the existing deployment task or add a second deployment task probably remains to be determined - but I think adding a second deployment task is "safer" - at least to begin with.

Faizi

A better suggestion would be to copy-and-modify the existing WFM so that your custom copy has the changes in it. Whether you want to change the existing deployment task or add a second deployment task probably remains to be determined - but I think adding a second deployment task is "safer" - at least to begin with.

Yes, I too mean to say that make a copy of OOTB workflow and make changes into this. Do not modify the OOTB worklow (default).