Reading WFM 's ipm File Using Java API

Hi,

TS version : 7.3
OS RHL

I want to read the WFM 's ipm file using Java. Since the IPM has the stucture of an XML file , can I use JAVA api's to read XML Nodes
I have a need to read the Task Properties in this ipm file. Can someone please tell me how can i implement this using java class .

Thanks.

Find more posts tagged with

Comments

Adam Stoller

I want to read the WFM 's ipm file using Java. Since the IPM has the stucture of an XML file , can I use JAVA api's to read XML Nodes
I have a need to read the Task Properties in this ipm file. Can someone please tell me how can i implement this using java class .

Perhaps if you explain a bit more about why you want to do this, we might be able to provide some guidance.

I don't remember for sure, but if it's not already in 7.3.1, then I think 7.3.2 begins to use both *.ipm and *.json files for the WFMs - so depending on what you're trying to do, you may end up having to rewrite it again afterwards - or there might be a completely different methodology you could use to achieve the actual desired goals.

Migrateduser

Which task properties do you need to see?

Nawin

Thanks for the quick response. I am explaining my need below.

For a new Release We create a new branch and we copy the WFMs configured for the previous Release branches. This copied WFM's ipm file contains references of ipl files from previous Release paths and we are manually configuiring them to the current ones.

say of instance, the command property of external task is having a ipl file reference as :

$IW_HOME/local/config/folder1/folder2/PreviousRelease/test.ipl

So we change it as,

$IW_HOME/local/config/folder1/folder2/PresentRelease/test.ipl

Hence We are planning to automate the whole process using Java. Please let me know if need more info on this.

Rick Poulin

When you stop manually configuring stuff, surely you'll be generating those path values using modeler variables and/or external tasks to compute the value of the IPL you want to use (which, by the way, seems a bit silly because you could just as well pass variables to a single IPL). Once you dynamically compute your "previous release", it shouldn't be too much of a stretch to extend that computation for "present release" without needing to read WFM files directly.

In any case, you'll probably have to start storing the "release ID" somewhere less manual -- perhaps an XML file somewhere or teamsite's edition functionality itself?