nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Debug LS WF

nipper

OK, I am trying to push 2 different branches to 2 different servers (one is a www site and one is an intranet).

So I used "Deploying Multiple Sites to Multiple Runtime Instances" instructions in the SP Dev Guide. Added a new bean (entry key="vip") for the vip site (new target node, path, etc), changed the Target node in the custom_instantiation.cfg (with a new label and I do see that new label), and changed the Global Variable (DeployFilesTargetNodes).

When I try to submit this with my new WF, I still see the deployments go to the original site (which corresponds to the bean (entry key="production") rather than the bean that should be read for the vip site.

I am at a loss as to how to debug furthur. I cannot see anything in the servletd log that indicates what bean is in use. There are no errors.

How can I debug this ?

Andy

Find more posts tagged with

Comments

nipper

I guess I am talking to myself. No problem.

Doing some debugging, I noticed that "production" was used in the Publish LiveSite Content xml (I edited the IPM by hand). I also noticed a place in custom_instantiation where it was used (even after I followed the instructions in the SP Dev Guide).

Net net is that currently I am pushing from one branch to one site and my second is currently deploying to the correct DB but no files are pushed.

I can certainly work around this (I have a publish edition step and I can run OD in there.) but I would really like something that can be supported when I am not around.

So back to my original question: Is there any ability to debug what is happening in a deploytask ? I cannot find any logs. Perl was easy, crack it open and turn debug on. How can I do that with a Java task ?

vpatel

So back to my original question: Is there any ability to debug what is happening in a deploytask ? I cannot find any logs. Perl was easy, crack it open and turn debug on. How can I do that with a Java task ?

Let me understand this correctly - you are trying to log the OOTB external task tied with OOTB Java class, correct? Let me also verify that you have checked servletd logs and you want to see more info than logged in there, correct?

You can try to turn the base loggers on and increase the logging level. See if that helps. At the end of the day if the Java class itself isn't logging some piece of information that you are after then updating the log level will not make much of a difference.

In any case, keep in mind that with perl, you have the source code versus Java what you have is the compiled version of it (JAR files) that you are referencing. I do not want to open up the religious war of Perl vs Java here but what is provided with PLC is written in Java. If increasing the logging level doesn't help then you might want to look into creating something custom that logs everything that is necessary for your requirement.

Also back to your original post, I am not sure exactly what sort of customization you have done to PLC WF. When you deploy content to "Production" using OOTB PLC, it will also sync up "Development" even if you selected "Production". I believe that is the behavior.

HTH!

report.zip

vpatel

So I used "Deploying Multiple Sites to Multiple Runtime Instances" instructions in the SP Dev Guide. Added a new bean (entry key="vip") for the vip site (new target node, path, etc), changed the Target node in the custom_instantiation.cfg (with a new label and I do see that new label), and changed the Global Variable (DeployFilesTargetNodes).

I am assuming you defined the corresponding bean and did a build.bat/build.sh?

print_several_times.rptdesign

nipper

Let me understand this correctly - you are trying to log the OOTB external task tied with OOTB Java class, correct? Let me also verify that you have checked servletd logs and you want to see more info than logged in there, correct?

You can try to turn the base loggers on and increase the logging level. See if that helps. At the end of the day if the Java class itself isn't logging some piece of information that you are after then updating the log level will not make much of a difference.

In any case, keep in mind that with perl, you have the source code versus Java what you have is the compiled version of it (JAR files) that you are referencing. I do not want to open up the religious war of Perl vs Java here but what is provided with PLC is written in Java. If increasing the logging level doesn't help then you might want to look into creating something custom that logs everything that is necessary for your requirement.

HTH!

Yep, I will forgo the religious war as well. You are correct in you questions, there is no usable information in the servletd logs. Just a bunch of true, false messages.

How do I check the base logger & increase the logging level ?

Got another Q VP, when you write your own WF for LiveSite, do you use some of the bundled jar files or are you creating your own ?

Thanks

Andy

vpatel

How do I check the base logger & increase the logging level ?

Go to http://your-ts-server/iw-cc/command/iw.base.loggers and find the package(s) for which you want to increase the log level and turn it on!

Got another Q VP, when you write your own WF for LiveSite, do you use some of the bundled jar files or are you creating your own ?

Totally depends on what a given external task is doing. For a simple deployment task, try to configure and use PLC as much as possible. If you need further customizations that do not easily fit into the OOTB stuff then you can create your own Java classes and reference any JAR files that you need as there is not point in re-inventing the wheel when some functionality is already present in the product.

For example, create your Java classes for the deployment task + any OD WS client and just reference OD WS JARs.

HTH!

vpatel

nipper

How do I figure which one to turn on ? From the, the task in question seem to be com.intoerwoven.livesite.sping.workflow.task.DelegatingUrlExternalTaskProxy

That (to me) seems to be a wrapper.

I can certainly blast a bunch and see what fits (which is what I am doing)

vpatel

If you aren't sure then just do any package name that contains "workflow" and "deployment" ;-)

nipper

Thanks, will do. I am seeing a Java error now - item being looked up not found, so I suspect that is why the 2nd deployment is not going. So I will start playing with the log settings.

I owe you dinner if we are ever in the same city at the same time.

Andy

Rob76

Hello

How did you end up resolving this? The article 60255 works great for adding another DB, but how did you end up deploying assets to the filesystem?

Would be nice not to hard code anything.

Thanks
Robert

nipper

What are you trying to do ? Have 3 levels of deployments, i.e. test, stage and prod ? Or, using 1 WF, push from branch1 to test and prod1 and from branch2 to test2 and prod2 ?

I was trying the latter and ended up copying the WF, making a second and pushing out to prod2 (though I am pretty certain I did not need to do that).

Rob76

I see what you are saying.

Trying to configure your first example. Where there is 1 Branch, which could deploy to dev(TeamSite), or to Stage/QA(runtime), or to Prod(runtime). Stage/QA should have the same function as prod, aside from deploying to different DBs and file systems.

Dev and Prod are what's configured OOTB. Just need to add Stage/QA.

Phase I is complete, which is to add the new DB node per article 60255. Phase II is to configure OD to deploy files to Stage/QA.

It would be great to be able to configure the "Production Deployment" task such that the file deployment would either go to Stage/QA or Production based what the user selected in the initial configuration screen.

The answer could lie in this class com.interwoven.livesite.spring.workflow.task.DelegatingUrlExternalTaskProxy

or this bean
workflow.task.HeadlessDeploymentTask

Where would I find that class to edit it?

Maybe there is a better way that I'm overlooking? Thoughts?

Thanks

Rob76

FYI, this was resolved per article 60255