PLC workflow customization

Hi All,

I am trying to customize the OOTB plc workflow, just wondering how the deployment to DEV is handled in PLC workflow. For production deployment, I can see entry in customer-teamsite-resource-config.xml file, and it is taking configurations from this file, while there is no such entry for development environment. Besides this, deployment tasks for dev and prod are using separate java beans and class files.

any pointer will be helpfull.

Thanks and Regards,
Jitu

Find more posts tagged with

Comments

nipper

Hi All,

I am trying to customize the OOTB plc workflow, just wondering how the deployment to DEV is handled in PLC workflow. For production deployment, I can see entry in customer-teamsite-resource-config.xml file, and it is taking configurations from this file, while there is no such entry for development environment. Besides this, deployment tasks for dev and prod are using separate java beans and class files.

any pointer will be helpfull.

Thanks and Regards,
Jitu

There are some threads on the LiveSite forum about this, pretty recent.

In a nutshell, the PLC deployment ignores the development target, so even if you add a bean (which you need to do) you also have to change the name from development to something else (preview).

You will need to change the PLC itself as well as the accompanying files. ALso will need to change the lscs config file to add that target.

Finally, on 7.2.1 you have to add the mega patch before you do this,

Adam Stoller

To add to what Nipper already said....

Rick Poulin

In a nutshell, the PLC deployment ignores the development target

Tiny clarification... the development target is ignored for the LSDS (file) deployment, but it's what deploys LSCS content to LSCSAuth. If you're still using LSCSAuth, don't get rid of the development target; *add* your new one.

g2svnit

Hi All,

Thanks for replies!

I will take care of mentioning teamsite version in future posts (Currently I am using Teamsite 7.2.1).

I am trying to customize PLC workflow for new environment, just wanted to understand how actually workflow works for Development environment (which is quite clear now).

I have added a new target environment to the PLC workflow, however my LSCS deployment is geting failed, lscs logs are showing below error:

LIB: 2012-11-14 04:25:45 Remote-ERROR: remote-dir-not-ok
LIB: 2012-11-14 04:25:45 ERROR: prepare-failed.
LIB: 2012-11-14 04:25:45 Receiver-ERROR: ERROR: [d:\lscsauth-store] is not an allowed deployment path.
LIB: 2012-11-14 04:25:45 ERROR: Failed to deploy local_directory[.] of area[D:\Interwoven\LiveSiteCSAuth\authoring\tmp\3268666e652e9fbab75523c9cdcdb6c2\payload] for filelist[D:\Interwoven\LiveSiteCSAuth\authoring\tmp\3268666e652e9fbab75523c9cdcdb6c2\filelist\lscs.filelist]
LIB: 2012-11-14 04:25:45 ERROR: Failed 1 of 1 filelists

However I have entry for "d:\lscsauth-store" under localhost in by "odbase.xml" file.

Note: I am attaching full log file with the post.

Thanks,
Jitu

nipper

Is d:\lscsauth-store listed on the receiver as a valid deployment target for this sender ?

Probably not

Rick Poulin

Is d:\lscsauth-store listed on the receiver as a valid deployment target for this sender ?

Log file name indicates he's deploying to localhost so the confusion is probably that his odbase.xml's allowedHosts says
<node host="localhost">
when it should actually say
<node host="actual.server.name.or.fqdn">

g2svnit

Hi,

I tried all possible options listed below but nothing worked.

(Note: My both Receiver and Sender are localhost only)

I created a simple deployment discriptor file and tried deployment to local host (through command prompt), but that too giving the same error (remote directory not ok, directory is not allowed deployment path) for any directory within D drive where my Interwoven is installed (I tried deploying at different location).

Thanks,
Jitendra

Adam Stoller

Please post the following information:

mart2001

How about putting

d:\lscsauth-store

in the of your teamsite server name? Do you have localhost in your odnodes.xml file?

You will need to specify the name in odnodes.xml in odbase.xml with the correct name.

Hi All,

Thanks for replies!

I will take care of mentioning teamsite version in future posts (Currently I am using Teamsite 7.2.1).

I am trying to customize PLC workflow for new environment, just wanted to understand how actually workflow works for Development environment (which is quite clear now).

I have added a new target environment to the PLC workflow, however my LSCS deployment is geting failed, lscs logs are showing below error:

LIB: 2012-11-14 04:25:45 Remote-ERROR: remote-dir-not-ok
LIB: 2012-11-14 04:25:45 ERROR: prepare-failed.
LIB: 2012-11-14 04:25:45 Receiver-ERROR: ERROR: [d:\lscsauth-store] is not an allowed deployment path.
LIB: 2012-11-14 04:25:45 ERROR: Failed to deploy local_directory[.] of area[D:\Interwoven\LiveSiteCSAuth\authoring\tmp\3268666e652e9fbab75523c9cdcdb6c2\payload] for filelist[D:\Interwoven\LiveSiteCSAuth\authoring\tmp\3268666e652e9fbab75523c9cdcdb6c2\filelist\lscs.filelist]
LIB: 2012-11-14 04:25:45 ERROR: Failed 1 of 1 filelists

However I have entry for "d:\lscsauth-store" under localhost in by "odbase.xml" file.

Note: I am attaching full log file with the post.

Thanks,
Jitu

g2svnit

Hi All,

The issue was due to un-encryption database password in the file livesite_database.xml, I encrypted the password using CLT and other errors automatically got resolve.

Thanks to All!
Regards,
Jitendra

sheikh1

I'm sure this error should not be from database password string.

ERROR: [d:\lscsauth-store] is not an allowed deployment path.

you must have added entries under both hostname and localhost