OK, Following up on a thread from a while ago. Figure I will post the status and see if anyone has any thoughts.
Running 721 with the mega-patch on Linux. Trying to add another node to the PLC workflow (a true preview node complete with LSDS deployments - we call it WIP). WIP will use the local LSCS/AT installed on the TS server.
Two assumptions that were made (confident they are valid but posting anyway):
- PLC preview deployment will only push data to the LSCS/AT instance and not push any content to LSDS servers
- Since lscs-authoring has preview and production nodes (in 721) you cannot add a custom one (WIP) - this functionality was added in 731 but that doesn't help much
- The section in the SP Developers Guide talking about adding nodes completely ignores lscs changes.
So I copied the production deploy step from the PLC and placed it just after the preview deploy, and changed the TargetNode to use the WIP Java bean:
[php]
false
true
false
Task
WIP_Deploy
$IW_USER
ItsURLTask
http://$IW_SERVER:$IW_PORT/iw-cc/urlexternaltask 477.75
$IW_WORKAREA
1077.0
ClassName=com.interwoven.livesite.spring.workflow.task.DelegatingUrlExternalTaskProxy|TaskBeanId=workflow.task.HeadlessDeploymentTask|odSubst_siteName=$IW_SCRIPT(GetSiteName)|TargetNodes=WIP
0
false
none
true
Deploys content and metadata to one or more target environments for WIP
[/php]
But this still kicks off the Production LSCS deployment (going to the LivesiteRuntime target), rather than the WIP target defined in the WIP bean.
If I cannot make this work, my thought is to replace the deployment step with a generic OD step (we do not have the DB enabled), because I only need LSDS. Should not be too hard, but I am not certain about clearing the cache.
Any tips/pointers/RTFMs ?
