Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Super Contributor.. d_shavrin Super Contributor..
Super Contributor..
313 views

connect-it - mapping generic question

Hello there,

I'm a beginner in connect-it, need some advices on mapping processes.

The scenario:

- source DB contains 3 fields: job_ID, job_name, status

- we need to do such thing: DB -> SOAP request based on 'job_name' field only -> update the status for the same job_ID in the same source table/

Question:

How to pass the job_ID from stage #1 (DB) to stage 3 (DB) if SOAP does not use and does not return it? 

Thank you!

Dima

0 Likes
4 Replies
Micro Focus Contributor
Micro Focus Contributor

Re: connect-it - mapping generic question

Hello Dima,

    There should be a response on the SOAP call, and you could use that response (or the default response) from the SOAP connector to make the action on the DB. If the flow is the same, then on the last connector, you should still be able to view the data from the parents (previous documents). 

     What exactly do you mean on the no response? To where is this request going to?

Regards, 

0 Likes
Highlighted
Super Contributor.. d_shavrin Super Contributor..
Super Contributor..

Re: connect-it - mapping generic question

hi,

Here's the scenario, we need to start the jobs based on DB content (Job_ID, Job_name, start_time, status) at some moments of times. The same job may need to be run of several moments, so we need to use  Job_ID (1,2,3..) as a key, not the job name. There may be workarounds, but I'd like to do it the following way:

1. at the right moment of time we SOAP request like 'start the job called JobX'

2. there's a separate ID for that job called Job_ID in the source DB. We don't use it in the SOAP request however at all.

3. now we request 'tell me the status of JobX' and get 'running' status.

4. now we need to set 'running' status in the relevant field of the database, but we should only rely on Job_ID, since there may be several lines with the same JobX job name.

Question: how to pass that Job_ID from the beginning to that final step?

Hope it is clear now.

Thank you,

Dima

0 Likes
Super Contributor.. d_shavrin Super Contributor..
Super Contributor..

Re: connect-it - mapping generic question

No advices in here?

0 Likes
Micro Focus Contributor
Micro Focus Contributor

Re: connect-it - mapping generic question

Hello,

     So, the scenario will make one execution per record in the DB, so if you have JOB_ID 1,2,3, that means that the logic will be execute three times for each JOB_ID. 

     If you want to have the JOB_ID available, you have to add it on the Produced document coming from the DB, it doesn't matter if you will not use it on the request, but to have it visible you have to consume it. 

    Once the request is done, on CIT you should be able to see (on the destination connector) the parent document,  [$ParentDoc$.JOB_ID] or similar, depending on the document structure. 

    If the status field is also on the produced document, then it should also be usable and visible, if not and its a foreign key to other table, then you might need to use a query function such as PifNewQueryFromFmtName(), you can see the Help for example usage. The parent available for each execution will only be one, so there should'nt be any need of doing additional queries.  

    You can see them more easily if you enable monitors, this will give you a visual debug of all the elements and their paths (Monitors-> Enable Monitors -> Normal processing / No filter under Session backups and Display Sessions).

Hope this helps,

Regards, 

Enrique Lobo

 

     

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.