startdeploy.sh VS PLC workflow

Hashaan

I am on TS 7.3.2, Solaris 5.10

 

I was tasked to deploy a set of DCRs to a configured LSCS server. I was just wandering around the devnet and I came up with startdeploy.sh , which pretty much does the same function as PLC( to my knowledge) ,the later is a CLT and the other is WFModel .

 

Can some one throw inputs or suggestions , indirectly I am looking for

 

1) pros and cons

2) Somewhere I noticed that the using one of these for deployments of XML of EA'a would vary

 

Thanks in advance

Hashaan

Sorry my bad , I have posted this in a TeamSite section rather it should be in LSCS.

Adam Stoller

startdeploy.sh works fine - at least for me (thanks to some help from @nipper )

The trick is to create the manifest file properly and then to pass the appropriate flags into the script.

 

The file would look something like this:

<?xml version="1.0" encoding="UTF-8"?>
<deployment>
 <context area="/default/main/.../WORKAREA/wa_name"/>
 <filelist>
  <file areaRelativePath="relative/path/to/file" otherAttributes="true"/>
  ...
 </filelist>
</deployment>

 Note: In order to get the EAs (or at least custom EAs, those not begining with TeamSite/Metadata/) deployed, make sure to have otherAttributes="true" - the documentation wasn't to clear about this, but it made a distinct difference for me.

 

The command line would then look look something like this:

startdeploy.sh -StartDeploy_OverrideManifest /path/to/manifest.xml -StartDeploy_DeploymentMode target-mode

 The target-mode is an entry key name from IWHOME/local/config/lib/content_center/livesite_customer_src/etc/conf/livesite_customer/resources/customer-teamsite-resource-config.xml

 

Hope that helps.

 

(Note: In my case, I wanted to push non-DCR XML files into LSCS purely to be able to query the data in / on them from some front-end code. I am not concerned about dependencies, LSDS, etc.)