PLC workflow doesn't start the deployment for lscs

Pauliw

Hi All ,

 

Issue: PLC worklow doesn't deploy files to runtime (LSCS - doesn't kicks the deployment meant for lscs), but deploys to LSDS .

 

 

Environment : windows server 2012 , teamSite 7.4.1 

 

This environment had only LSDS in runtime till yesterday, and i had installed LSCS recently.

 

After checking the settings in

 

1) lscs-authoring.xml  for runtime mode .

 

<runtime mode="production" lscsContext="lscs" lscsRuntimeTransport="http" lscsRuntimeHostname="localhost" lscsRuntimePort="1876" destinationArea="C:/LSCSRT-Store" destinationNode="LSCSRuntime"/>

 

2) Bean ID in customer-teamsite-resource-config.xml under C:\Interwoven\TeamSite\local\config\lib\content_center\livesite_customer_src\etc\conf\livesite_customer\resources

 

<bean id="customer.teamsite.DeploymentService.OpenDeploy.DeploymentTargetMap"
parent="teamsite.DeploymentService.OpenDeploy.DeploymentTargetMap">

 

 

3) checked for lscs.enabled=false and changed it to "true"

 

I have initiated the PLC workflow for the deployment verifying the above 3 , I could see that the deloyment configuration OpenDeployWebRoot gets initiated and deploys the files to LSDS, but not the one for lscs. 

 

 

 

Also, i did execute the post installation steps for LSCS 

 

startdeploy.bat -StartDeploy_DeploymentMode production -StartDeploy_TsAreaDiffArea //<auth-host>/default/main/testrt/ STAGING -StartDeploy_TsAreaDiffPreviousArea //<auth-host>/
default/main/testrt/EDITION/INITIAL

 

But it gave me an error.

****

[ERROR] 20:48:07 StartDeployment - Exception in StartDeployment.main()
org.jasypt.exceptions.EncryptionInitializationException: java.security.NoSuchAlgorithmException: PBEWithMD5AndDES SecretKeyFactory
at org.jasypt.encryption.pbe.StandardPBEByteEncryptor.initialize(StandardPBEByteEncryptor.java:597)

****

 

 

Can you please let me know is there are any more property files i have to look to initate the deployment for lscs OOTB.

 

 

Thanks

Paul

Rick Poulin

Did you run the build.bat after making the change in #3? It sounds like you didn't, because OpenDeployWebRoot should not be fired off when lscs.enabled=true

 

As for the encryption issue, that's a new one for me. Usually your key might not be correctly encoded, but for it not to find the algorithm at all implies that you have a classpath problem somehow.