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; } } }

Understanding Publish LiveSite Content Workflow

keithcolb

TS 7.2
Win 2003 Server

Recently upgraded to 7.2 and using the PLC workflow. Previously handled much of the workflow through perl and now it's java. Having a problem finding source code for things such as DeploymentTask and WebTask and so on. My java is not on the same level as my perl, and not even sure I can view source code (jar files?), etc.

Basically I'd like to see where the workflow actually calls the OpenDeployWebRoot deployment config. I'd like to be able to reduce customization and just change what deployment config is being used or alternately change the variables in the OpenDeployWebRoot deployment config.

Anything helps, thanks

Find more posts tagged with

Comments

mart2001

No, you won't be able to see the source code to the jar files. You'll need to unjar (similar to untar) the files, then de-compile the class files in order to see the source code, but doing so could be violating the contracts you have with Interwoven.

I think the od webroot deploy config should be stored in the workflow variable or task variable.

srosewall

Basically I'd like to see where the workflow actually calls the OpenDeployWebRoot deployment config. I'd like to be able to reduce customization and just change what deployment config is being used or alternately change the variables in the OpenDeployWebRoot deployment config.

You need to introduce yourself to the Spring beans which work with the Java code in the WFM.

Take a look in ApplicationContainer\server\default\deploy\iw-cc.war\WEB-INF\conf\livesite\resourcesteamsite-resource-config.xml and find the deployment descriptors. These use pattern matching to work out which OD config should be used for which asset being deployed. You can override these definitions with custom beans if you want to change the configuration. The override beans should be defined in customer-teamsite-resource-config.xml which is located in the livesite_customer_src toolkit ready for building.

Note: there's also a set of descriptors for LSCS in a separate xml file - lscs-resource-config.xml

keithcolb

Thanks for the responses.

Looks fairly straight-forward to change the OpenDeployWebRoot bean and override it with something custom.

I can see how the HeadlessDeployment Task calls the Deployment Descriptors. The problem is that I want to keep the OpenDeployWebRoot config and create another similar deployment config for use with another workflow. I don't want to limit based on filtering, I want to decide which to use based on what workflow is selected.

Maybe I can use another deployment bean in the workflow config to point to a different deployment descriptor defined in the customer config.

There is a small section in the SitePub Dev Guide on deployment customization but it doesn't cover this.

Any ideas?

02insp_by_sup.rptdesign

keithcolb

I found a solution.

Just added custom beans to the livesite_customer toolkit and it worked. Wasn't sure I could put the workflow bean in customer config but I could.

Thanks

PaulW

I cant see any references in any of the config files to the standard lscs configs. is there anyway to apply a filter to these deployments, to prevent assets from being deployed to lscs?

e.g. teamsitearea-diff