Custom OD Deployment not starting in PLC

Hi,

I want to deploy static content to a different path on LSDS server than the livesite pages, I tried creating a new definition in commit-deploy-plc.xml but it didn't work , I raised a case for the same to Interwoven support and got to know that new definition cannot be added in commit-deploy-plc.xml and it wont work , so I had to resort to adding a new bean in customer-teamsite-resource-config.xml to invoke the deployment for static content. I have added a bean for Custom Datadeploy in customer-teamsite-resource-config.xml and it is working perfectly fine but the OD bean is not working. I have earlier run the same OD bean successfully on Teamsite 7.1 but same thing is not working on 7.3.1 .
Below is my Bean in customer-teamsite-resource-config.xml :

<bean id="customer.teamsite.DeploymentService.DeploymentDescriptors" parent="teamsite.DeploymentService.DeploymentDescriptors">
<property name="sourceList">

<list merge="true">

<bean class="com.interwoven.livesite.opendeploy.impl.DataDeploymentDescriptor">
<property name="name" value="pageMetadata"/>
<property name="configFile" value="LiveSite/pageMetadata"/>
<property name="failOnError" value="true"/>
<property name="filterPatterns">
<bean class="com.interwoven.livesite.common.util.PatternWrapper" factory-method="createList">
<constructor-arg>
<list>
<value>+.*\.page</value>
</list>
</constructor-arg>
</bean>
</property>
</bean>

<bean class="com.interwoven.livesite.opendeploy.impl.OpenDeploymentDescriptor">
<property name="name" value="WebLivesiteDeployment" />
<property name="configFile" value="LiveSite/WebLivesiteDeployment" />
<property name="failOnError" value="true" />
<property name="filterPatterns">
<bean class="com.interwoven.livesite.common.util.PatternWrapper" factory-method="createList">
<constructor-arg>
<list>
<value>-.*iw/compXSL/head.xsl$</value>
</list>
</constructor-arg>
</bean>
</property>
</bean>

</list>
</property>

</bean>

Please can anybody why "com.interwoven.livesite.opendeploy.impl.OpenDeploymentDescriptor" bean is not working in Teamsite 7.3.1 ?

Thanks !

Regards,
Ankit

Find more posts tagged with

Comments

Bowker

We had a similar requirement - deploy static content to a second folder structure. This will not prevent the first copy from going to the normal LiveSite folder, but in the end that was a good thing. We could then test pages going directly to the LSDS server and it would pick up the static content (images...) if necessary.

Do do this we just added a new deployment to /conf/LiveSite/OpenDeployWebRoot.xml to deploy our static content to the second directory structure. No java code needed.

[PHP]

:
:

:

[/PHP]

TeamsiteDev

Hi Dan,

Thanks for your reply ! I am currently on TS 7.3.1 version, in this verison , if LSCS deployment has been enabled then LiveSite/OpenDeployWebroot.xml deployment is not triggered, only lscs/commit-deploy-plc.xml deployment is invoked .
I have currently used the solution you have suggested i.e . creating a new <filelist> within the same definition. This works fine if target paths for all sites & environments is same. We have two sites on same Teamsite and target path for static contents will be different for the sites. Hard-coding the target path in definiton will be a problem when target paths are different , thats why I wanted to keep a separate deployment descriptor for Static content so that I can define the target paths in the replicationFarms of each site and environment instead of defining it in <definition> but the OD bean is just not working in 7.3.1.

Thanks !

Regards,
Ankit

Adam Stoller

FWIW - the current project I'm on has a similar, but different, requirement - in that the static content (.css, .js, .html, etc.) gets deployed to web servers and the other content (templatedata, .page, .xsl, etc.) gets deployed to LSCS / LSDS servers.

In our case (7.2.1 Patch 1 on Linux with WebSphere) - we already had a custom variant of the PLC workflow, so we just added another task to handle the static asset deployments and used filters to ensure that only the appropriate files go to the appropriate target farms.

True, it's not the "elegant" way to do it with beans and such, but it does work ...

image #1.png

image #2.png

Vendim Birbili

Hi,

I want to deploy static content to a different path on LSDS server than the livesite pages, I tried creating a new definition in commit-deploy-plc.xml but it didn't work , I raised a case for the same to Interwoven support and got to know that new definition cannot be added in commit-deploy-plc.xml and it wont work , so I had to resort to adding a new bean in customer-teamsite-resource-config.xml to invoke the deployment for static content. I have added a bean for Custom Datadeploy in customer-teamsite-resource-config.xml and it is working perfectly fine but the OD bean is not working. I have earlier run the same OD bean successfully on Teamsite 7.1 but same thing is not working on 7.3.1 .
Below is my Bean in customer-teamsite-resource-config.xml :

<bean id="customer.teamsite.DeploymentService.DeploymentDescriptors" parent="teamsite.DeploymentService.DeploymentDescriptors">
<property name="sourceList">

<list merge="true">

<bean class="com.interwoven.livesite.opendeploy.impl.DataDeploymentDescriptor">
<property name="name" value="pageMetadata"/>
<property name="configFile" value="LiveSite/pageMetadata"/>
<property name="failOnError" value="true"/>
<property name="filterPatterns">
<bean class="com.interwoven.livesite.common.util.PatternWrapper" factory-method="createList">
<constructor-arg>
<list>
<value>+.*\.page</value>
</list>
</constructor-arg>
</bean>
</property>
</bean>

<bean class="com.interwoven.livesite.opendeploy.impl.OpenDeploymentDescriptor">
<property name="name" value="WebLivesiteDeployment" />
<property name="configFile" value="LiveSite/WebLivesiteDeployment" />
<property name="failOnError" value="true" />
<property name="filterPatterns">
<bean class="com.interwoven.livesite.common.util.PatternWrapper" factory-method="createList">
<constructor-arg>
<list>
<value>-.*iw/compXSL/head.xsl$</value>
</list>
</constructor-arg>
</bean>
</property>
</bean>

</list>
</property>

</bean>

Please can anybody why "com.interwoven.livesite.opendeploy.impl.OpenDeploymentDescriptor" bean is not working in Teamsite 7.3.1 ?

Thanks !

Regards,
Ankit

I think you are missing the bean id. can you send the whole customer-teamsite-resource file?

TeamsiteDev

Hi,

I did double check the bean name and I have earlier ran the same bean successfully on 7.1 version but that was without LSCS . In 7.3.1 when LSCS is enabled , commit-deploy-plc OD deployment takes precedence over all other OD deployments and doesn't allow other OD deployments to run. Thats the reason , DD is running fine but OD bean is being suppressed. Interwoven support have also accepted this as a bug in 7.3.1 PLC . Only way out is to add a separate external task for Static content deployment as suggested by Ghoti.

Regards,
Ankit

Vendim Birbili

Hi,

Only way out is to add a separate external task for Static content deployment as suggested by Ghoti.

Regards,
Ankit

so by adding another external task to the PLC workflow you are adding a new targetNode and you modified all the configuration files to include that target?? can you provide more insight if you can?

thanks

TeamsiteDev

targetNode values are picked from lscs-authoring.xml & customer-teamsite-resource-config.xml and same node values are mentioned in custom_instantiation.cfg or workflow initial screen.
In my external task , I created a task variable and set its value to the Target nodes variable ( $IW_CV(TargetNodes) ) . This way I can get the targetnode value in my perl script and I pass that value through a variable to my deployment descriptor , I have created replicationFarms of the same name as targetNodes in my deployment descriptor just the way they are in commit-deploy-plc.xml .