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; } } }

wfm_instantiator??

kaalraa

Hi all,

In WFT we have iwwft_instantiator.cgi to initiate a workflow. Could anyone provide me any pointer or suggestion as if there is a command similar to that within Workflow Modeler??

My requirement is to initiate a workflow (.ipm) from an application server based on certain params. Apart from that, is it feasible to callback to the Appln DB using a WSDL, so that before completion of all tasks, workflow could update the DB status field??

Thanks.

Find more posts tagged with

Comments

Faizi

Hi all,

In WFT we have iwwft_instantiator.cgi to initiate a workflow. Could anyone provide me any pointer or suggestion as if there is a command similar to that within Workflow Modeler??

My requirement is to initiate a workflow (.ipm) from an application server based on certain params. Apart from that, is it feasible to callback to the Appln DB using a WSDL, so that before completion of all tasks, workflow could update the DB status field??

Thanks.

Hi Kaalraa,
There is no such command like iwwft_instantiator.cgi, but you can try iwmodelc.exe command utility to instantiating a WFM workflow.
Another way might be using CSSDK to instantiate the workflow.
HTH,

Migrateduser

Hi Kaalraa,
There is no such command like iwwft_instantiator.cgi, but you can try iwmodelc.exe command utility to instantiating a WFM workflow.
Another way might be using CSSDK to instantiate the workflow.
HTH,

How does one use the CSSDK to instantiate a WFM workflow? I can see where you can instantiate a job based on an XML job spec:

CSWorkflowEngine.createWorkflow(String job_spec);

But I don't see a method that will initiate a workflow created with WFM. Or can you turn your WFM workflow into a job spec and then kick it off with the createWorkflow() method?

To add another twist, I'd like to kick off a WFM workflow using the CSSWDK and pass it the list of files I want to attach. Is this possible? I'm not seeing it...

Migrateduser

The lack of response to my questions leads me to believe there may not be an answer...which is troubling.

Did Interwoven drop the ball on this one? How could they tout WFM as the "best practice" way of building workflows and then include only a method to instantiate a job spec and not include a method to instantiate a WFM workflow in their SDK?

Faizi

How does one use the CSSDK to instantiate a WFM workflow? I can see where you can instantiate a job based on an XML job spec:

CSWorkflowEngine.createWorkflow(String job_spec);

But I don't see a method that will initiate a workflow created with WFM. Or can you turn your WFM workflow into a job spec and then kick it off with the createWorkflow() method?

To add another twist, I'd like to kick off a WFM workflow using the CSSWDK and pass it the list of files I want to attach. Is this possible? I'm not seeing it...

Due to engrosses i couldn't replied your question.

As you asked regarding WFM instantiation with CSSDK. Let me clear that i didn't tried it yet. It is based on my assumption with the help of docs.

WFM's instantiation screen creation and Running a Workflow is two different process. CSSDK role played after the job specification file creation. So your assumption is right. First create a job specification file with the "debug" option and save it. Now pass it the method:
CSWorkflowEngine.createWorkflow(String job_spec);

While attaching a file with workfow in this scenario would be a different way. Because it doesn't support the PreProcessor and PostProcesser commands. So another possible way might with adding a URL Task and try to attach the files within this task with the help of CSSWDK.

HTH

Adam Stoller

To play Devil's (i.e.: Smitty's :-) Advocate:

With WFTs you could use iwjobc (-i or with iwinvokejob) to initiate a workflow from a jobspec - but you also have the ability to use iwwft_compile.ipl to initiate a workflow directly from a WFT (where you provide an XML file with the inputs to the TAG_info() fields that normally would be interactive)

With CSSDK it is unclear if you can do the latter (with either WFTs or WFMs) as it seems to require a jobspec.

I imagine someone could reverse-engineer iwwft_compile.ipl to figure out how to write the same pre-processing routines for WFTs in Java, and possibly to do the same with WFMs (does iwmodelc provide for the instantiation of WFMs directly with inputs? I seem to recall that it's come up in threads, but don't remember the details right now) ... the bigger question is: if it is possible, why doesn't IWOV provide it as OOTB (or out of the CSSDK) functionality? If it isn't possible, it seems like a gaping hole that should be filled in.

To the latter end - I'd recommend putting this into a Support Case and filing it as a FR (one might say "bug", but chances are they'll see it as an FR)

Migrateduser

Thanks for the responses. I particularly liked being associated with Satan. I take it as a compliment! Smiley Surprised

)

I did open a support case and right after I opened the case, my support account was created for my new company and I now can't access my previously opened support cases, so I am trying to rectify that with IW Support.

I am disappointed that the functionality doesn't exist OOTB to do what seems like a common sense opperation. The fact that they actually gave us a method to initiate a job from a job spec makes it even more irritating. But it doesn't surprise me either.

I suppose another option would be to nest the workflows I want to initiate into the initial workflow. That wouldn't be a terrible option in this case, but I will have to play with it and see what nesting looks like to the user as far as the initial WF. I haven't done any nesting in a while, but I do recall that there were some undesirable byproducts from nesting that may make the appearance of the initial job confusing to the user. I recall that the endtask shows up in the task list or something ...but maybe they fixed that. Or maybe I'm just confused - that would explain a lot.

I appreciate the feedback. I'll let you know if I discover anything useful from the support case.

Bjorn

So Dave, did anything ever come of this bad boy? Or are we still screwed?

I appreciate the feedback. I'll let you know if I discover anything useful from the support case.

Migrateduser

So Dave, did anything ever come of this bad boy? Or are we still screwed?

I was never able to transfer the support case from my previous company to my new company, so it sort of died a slow death. And I never did have to follow through with it because we ended up not needing that finctionality. We simply create job specs from within our Java code and kick off the new workflows via the:

CSWorkflowEngine.[size=2]createWorkflow(String jobSpecification);

method. It works, and that is how we chose to do things here. Any workflows we have created to be executed via the command line via cron are created as job specs, not WFM workflows, so again they can be kicked off the old fashioned way, via CLTs.

So I don't know if there is a way to solve the original problem. If you find a solution, please do let me know.

[/size]

Brittany

Hi all,
I'm trying to use createWorkflow () but i keep getting a runtime error that's very generic (Failure in Operation). Here's my code. Can anyone see something that I'm doing wrong?


public class NestedSpec implements CSURLExternalTask {

    /**
     * Constructure.  Gets a handle on the logger.
     */
    public NestedSpec() {
        log = Logger.getLogger(getClass().getName());
    }

      public void execute(CSClient client, CSExternalTask currentTask, Hashtable params) throws CSException {
           log.error("Got into this class!");

            String groupName;

            CSWorkflowEngine workflowEngine = client.getWorkflowEngine();

             log.error("Got the engine: "+workflowEngine);

             String jobSpec = "usr/app/interwoven/TeamSite/tmp/AsynchronousTranslation.xml";
            CSWorkflow workflow =  workflowEngine.createWorkflow(jobSpec);


         } // end of execute() body


        /** Logger to use to log errors */
    Logger log;

}

Thanks

Adam Stoller

What do you see getting logged? Anything?
Did you make sure that you capture any exceptions thrown by all of the methods that throw them so that you can attempt to pinpoint the source of where things go wrong?

Brittany

So below is the stack trace from my error

com.interwoven.cssdk.common.CSException: (Failure in operation)
at com.interwoven.cssdk.sci.exception.ExceptionHandler.handleExceptionSci(ExceptionHandler.java:258)
at com.interwoven.cssdk.sci.exception.ExceptionHandler.handleException(ExceptionHandler.java:102)
at com.interwoven.cssdk.sci.workflow.WorkflowServiceSciImpl.createWorkflow(WorkflowServiceSciImpl.java:752)
at com.interwoven.cssdk.workflow.java.WorkflowServiceAdapterImpl.createWorkflow(WorkflowServiceAdapterImpl.java:78)
at com.interwoven.cssdk.workflow.impl.CSWorkflowEngineImpl.createWorkflow(CSWorkflowEngineImpl.java:225)
at com.ul.wfm.NestedSpec.execute(Unknown Source)
at com.interwoven.ui.teamsite.workflow.task.URLExternalTaskCommand.execute(URLExternalTaskCommand.java:109)
at com.interwoven.ui.base.impl.command.CommandHandler.doExecuteCommand(CommandHandler.java:917)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandDescriptor(CommandHandler.java:753)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunForward(CommandHandler.java:650)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandID(CommandHandler.java:594)
at com.interwoven.ui.base.impl.command.CommandHandler.runCommandLoop(CommandHandler.java:233)
at com.interwoven.ui.base.impl.command.CommandServlet.doGet(CommandServlet.java:163)
at com.interwoven.ui.base.impl.command.CommandServlet.doPost(CommandServlet.java:263)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at com.interwoven.ui.base.impl.command.CommandServletMapper.doGet(CommandServletMapper.java:90)
at com.interwoven.ui.base.impl.command.CommandServletMapper.doPost(CommandServletMapper.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at com.interwoven.ui.base.impl.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:203)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at com.interwoven.ui.base.util.SetRequestEncodingFilter.doFilter(SetRequestEncodingFilter.java:106)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:595)

From logging that I put in i can tell the problem is with this line specifically. But i can't figure out why.


CSWorkflow workflow = workflowEngine.createWorkflow(jobSpec);

Adam Stoller

...
From logging that I put in i can tell the problem is with this line specifically. But i can't figure out why.
CSWorkflow workflow = workflowEngine.createWorkflow(jobSpec);

Right, but that method can throw any one of five exceptions according to the java docs:

Crsb

as Ghoti mentioned, the path of the job spec file is most likely wrong.
is it "/usr/app/interwoven/TeamSite/tmp/AsynchronousTranslation.xml" or "usr/app/interwoven/TeamSite/tmp/AsynchronousTranslation.xml"?

assuming the path was correct, did you test your job spec file to see if it is valid using iwjobc?

Migrateduser

You then showed:
 CSWorkflow workflow = workflowEngine.createWorkflow(jobSpec);
Maybe it's just me - but my reading of the javadocs makes me think that this method may be expecting the actual XML string and not a path to a file - so you may have to read the contents of that file into a String and then pass that to this method in order for it to work.

Ghoti is also correct about what the createWorkflow() method is expecting as a parameter. It wants a job spec represented as a String. Not the path to the job spec. You must read the javadocs if you are trying to use the CSSDK. It tells you quite clearly what the input parameter should be:

createWorkflow

CSWorkflow createWorkflow(java.lang.String workflowSpecification) throws CSAuthorizationException, CSRemoteException, CSExpiredSessionException, CSException

Instantiate a workflow from an XML workflow job specification.

Parameters:: workflowSpecification - A valid XML workflow job specification

scriptedDataSetExample.zip

Brittany

Thank you, that was the problem. I put the actual xml into the string and escaped all of the quotes and it worked perfectly. Thanks again