Anonymous_User Absent Member.
Absent Member.
310 views

Changing the URL of an integration activity

In a workflow, in an integration activity.

I find it quite hard to change which URI the integraition activity is
pointing to.

There is a data item mapping, which I can change to be another soap
endpoint Envelope/@_serverUrl_ here, I can use a GCV, which mean, that I
thought that i could change the url.

That did not work.

If I "edit" the integration activity, and look at the input (top left
corner=, there is an "_serverUrl_" attribute. Which points to the URL of
the system i copied the workflow from. I cannot seem to get to edit that
url.

My question is, can I copy a workflow from one system to another, and make
adjustments to which URL is called? (from time to time, the IDM url itself
changes from IDM to IDMProv, and default ports differ between versions,
and I thought I would be safe, if I just corrected the wsdl to point to
localhost, but on this new system, UA does not listen on localhost)





Labels (1)
0 Likes
7 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Changing the URL of an integration activity

On Thu, 17 Dec 2015 15:19:43 +0000, Nicolai Jensen wrote:

> In a workflow, in an integration activity.
>
> I find it quite hard to change which URI the integraition activity is
> pointing to.
>
> There is a data item mapping, which I can change to be another soap
> endpoint Envelope/@_serverUrl_ here, I can use a GCV, which mean, that I
> thought that i could change the url.
>
> That did not work.
>
> If I "edit" the integration activity, and look at the input (top left
> corner=, there is an "_serverUrl_" attribute. Which points to the URL of
> the system i copied the workflow from. I cannot seem to get to edit that
> url.
>
> My question is, can I copy a workflow from one system to another, and
> make adjustments to which URL is called? (from time to time, the IDM url
> itself changes from IDM to IDMProv, and default ports differ between
> versions, and I thought I would be safe, if I just corrected the wsdl to
> point to localhost, but on this new system, UA does not listen on
> localhost)



Answering myself here.
I could just click on the "source" tab, instead of the "Tree" tab.
Then I could fix the url.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Changing the URL of an integration activity

On Thu, 17 Dec 2015 15:32:53 +0000, Nicolai Jensen wrote:

> On Thu, 17 Dec 2015 15:19:43 +0000, Nicolai Jensen wrote:
>
>> In a workflow, in an integration activity.
>>
>> I find it quite hard to change which URI the integraition activity is
>> pointing to.
>>
>> There is a data item mapping, which I can change to be another soap
>> endpoint Envelope/@_serverUrl_ here, I can use a GCV, which mean, that
>> I thought that i could change the url.
>>
>> That did not work.
>>
>> If I "edit" the integration activity, and look at the input (top left
>> corner=, there is an "_serverUrl_" attribute. Which points to the URL
>> of the system i copied the workflow from. I cannot seem to get to edit
>> that url.
>>
>> My question is, can I copy a workflow from one system to another, and
>> make adjustments to which URL is called? (from time to time, the IDM
>> url itself changes from IDM to IDMProv, and default ports differ
>> between versions, and I thought I would be safe, if I just corrected
>> the wsdl to point to localhost, but on this new system, UA does not
>> listen on localhost)

>
>
> Answering myself here.
> I could just click on the "source" tab, instead of the "Tree" tab. Then
> I could fix the url.


I was so wrong.
Changes in the "source" tab are not saved.

So back to my question.

Can I copy a workflow from one system to another, and make adjustments to
which URL is called in integration activities?

0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing the URL of an integration activity

On 12/17/2015 10:49 AM, Nicolai Jensen wrote:
> On Thu, 17 Dec 2015 15:32:53 +0000, Nicolai Jensen wrote:
>
>> On Thu, 17 Dec 2015 15:19:43 +0000, Nicolai Jensen wrote:
>>
>>> In a workflow, in an integration activity.
>>>
>>> I find it quite hard to change which URI the integraition activity is
>>> pointing to.
>>>
>>> There is a data item mapping, which I can change to be another soap
>>> endpoint Envelope/@_serverUrl_ here, I can use a GCV, which mean, that
>>> I thought that i could change the url.
>>>
>>> That did not work.
>>>
>>> If I "edit" the integration activity, and look at the input (top left
>>> corner=, there is an "_serverUrl_" attribute. Which points to the URL
>>> of the system i copied the workflow from. I cannot seem to get to edit
>>> that url.
>>>
>>> My question is, can I copy a workflow from one system to another, and
>>> make adjustments to which URL is called? (from time to time, the IDM
>>> url itself changes from IDM to IDMProv, and default ports differ
>>> between versions, and I thought I would be safe, if I just corrected
>>> the wsdl to point to localhost, but on this new system, UA does not
>>> listen on localhost)

>>
>>
>> Answering myself here.
>> I could just click on the "source" tab, instead of the "Tree" tab. Then
>> I could fix the url.

>
> I was so wrong.
> Changes in the "source" tab are not saved.
>
> So back to my question.
>
> Can I copy a workflow from one system to another, and make adjustments to
> which URL is called in integration activities?


One of the clever things they did in the IA changes from 4.01 to 4.02
(Well it was really in some AU, and I cannot be bothered to look which
one, but now so long in the past, it is history).

I discussed this whole issue here:

http://www.netiq.com/communities/cool-solutions/looking-at-the-new-integration-activity-approach-part-1
http://www.netiq.com/communities/cool-solutions/looking-at-the-new-integration-activity-approach-part-2


Anyway, the key is, as you noted the _serverURL_ is added by default.
You would set it in the pre-activity of the IA, on the workflow tab. I
think you referenced trying that...

Then there is ECMA inside the bottom of the IA, that reads that out,
sets the endpoint, and then removes it from the XML. I suspect
sometihng is broken in there, if the first change is not working for you.

Basically, find the place in the actual web services call, in the IA
view, that sets the URL and you will see ecma parsing out the XML. If
not, it is broken (make a new one and compare).


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Changing the URL of an integration activity

On Thu, 17 Dec 2015 16:03:16 +0000, Geoffrey Carman wrote:

> On 12/17/2015 10:49 AM, Nicolai Jensen wrote:
>> On Thu, 17 Dec 2015 15:32:53 +0000, Nicolai Jensen wrote:
>>
>>> On Thu, 17 Dec 2015 15:19:43 +0000, Nicolai Jensen wrote:
>>>
>>>> In a workflow, in an integration activity.
>>>>
>>>> I find it quite hard to change which URI the integraition activity is
>>>> pointing to.
>>>>
>>>> There is a data item mapping, which I can change to be another soap
>>>> endpoint Envelope/@_serverUrl_ here, I can use a GCV, which mean,
>>>> that I thought that i could change the url.
>>>>
>>>> That did not work.
>>>>
>>>> If I "edit" the integration activity, and look at the input (top left
>>>> corner=, there is an "_serverUrl_" attribute. Which points to the URL
>>>> of the system i copied the workflow from. I cannot seem to get to
>>>> edit that url.
>>>>
>>>> My question is, can I copy a workflow from one system to another, and
>>>> make adjustments to which URL is called? (from time to time, the IDM
>>>> url itself changes from IDM to IDMProv, and default ports differ
>>>> between versions, and I thought I would be safe, if I just corrected
>>>> the wsdl to point to localhost, but on this new system, UA does not
>>>> listen on localhost)
>>>
>>>
>>> Answering myself here.
>>> I could just click on the "source" tab, instead of the "Tree" tab.
>>> Then I could fix the url.

>>
>> I was so wrong.
>> Changes in the "source" tab are not saved.
>>
>> So back to my question.
>>
>> Can I copy a workflow from one system to another, and make adjustments
>> to which URL is called in integration activities?

>
> One of the clever things they did in the IA changes from 4.01 to 4.02
> (Well it was really in some AU, and I cannot be bothered to look which
> one, but now so long in the past, it is history).
>
> I discussed this whole issue here:
>
> http://www.netiq.com/communities/cool-solutions/looking-at-the-new-

integration-activity-approach-part-1
> http://www.netiq.com/communities/cool-solutions/looking-at-the-new-

integration-activity-approach-part-2
>
>
> Anyway, the key is, as you noted the _serverURL_ is added by default.
> You would set it in the pre-activity of the IA, on the workflow tab. I
> think you referenced trying that...
>
> Then there is ECMA inside the bottom of the IA, that reads that out,
> sets the endpoint, and then removes it from the XML. I suspect
> sometihng is broken in there, if the first change is not working for
> you.
>
> Basically, find the place in the actual web services call, in the IA
> view, that sets the URL and you will see ecma parsing out the XML. If
> not, it is broken (make a new one and compare).



Nice articles.
I got it working now.
Thank you very much.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing the URL of an integration activity

On 12/17/2015 11:22 AM, Nicolai Jensen wrote:
> On Thu, 17 Dec 2015 16:03:16 +0000, Geoffrey Carman wrote:
>
>> On 12/17/2015 10:49 AM, Nicolai Jensen wrote:
>>> On Thu, 17 Dec 2015 15:32:53 +0000, Nicolai Jensen wrote:
>>>
>>>> On Thu, 17 Dec 2015 15:19:43 +0000, Nicolai Jensen wrote:
>>>>
>>>>> In a workflow, in an integration activity.
>>>>>
>>>>> I find it quite hard to change which URI the integraition activity is
>>>>> pointing to.
>>>>>
>>>>> There is a data item mapping, which I can change to be another soap
>>>>> endpoint Envelope/@_serverUrl_ here, I can use a GCV, which mean,
>>>>> that I thought that i could change the url.
>>>>>
>>>>> That did not work.
>>>>>
>>>>> If I "edit" the integration activity, and look at the input (top left
>>>>> corner=, there is an "_serverUrl_" attribute. Which points to the URL
>>>>> of the system i copied the workflow from. I cannot seem to get to
>>>>> edit that url.
>>>>>
>>>>> My question is, can I copy a workflow from one system to another, and
>>>>> make adjustments to which URL is called? (from time to time, the IDM
>>>>> url itself changes from IDM to IDMProv, and default ports differ
>>>>> between versions, and I thought I would be safe, if I just corrected
>>>>> the wsdl to point to localhost, but on this new system, UA does not
>>>>> listen on localhost)
>>>>
>>>>
>>>> Answering myself here.
>>>> I could just click on the "source" tab, instead of the "Tree" tab.
>>>> Then I could fix the url.
>>>
>>> I was so wrong.
>>> Changes in the "source" tab are not saved.
>>>
>>> So back to my question.
>>>
>>> Can I copy a workflow from one system to another, and make adjustments
>>> to which URL is called in integration activities?

>>
>> One of the clever things they did in the IA changes from 4.01 to 4.02
>> (Well it was really in some AU, and I cannot be bothered to look which
>> one, but now so long in the past, it is history).
>>
>> I discussed this whole issue here:
>>
>> http://www.netiq.com/communities/cool-solutions/looking-at-the-new-

> integration-activity-approach-part-1
>> http://www.netiq.com/communities/cool-solutions/looking-at-the-new-

> integration-activity-approach-part-2
>>
>>
>> Anyway, the key is, as you noted the _serverURL_ is added by default.
>> You would set it in the pre-activity of the IA, on the workflow tab. I
>> think you referenced trying that...
>>
>> Then there is ECMA inside the bottom of the IA, that reads that out,
>> sets the endpoint, and then removes it from the XML. I suspect
>> sometihng is broken in there, if the first change is not working for
>> you.
>>
>> Basically, find the place in the actual web services call, in the IA
>> view, that sets the URL and you will see ecma parsing out the XML. If
>> not, it is broken (make a new one and compare).

>
>
> Nice articles.


Glad to help, send fish. I love herring. (Someone actually mailed me
herring!!)

> I got it working now.
> Thank you very much.


What specifically did you do to fix it? (For the record, and the next
person with the same issue and finds this in Google).


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Changing the URL of an integration activity

On Thu, 17 Dec 2015 16:39:22 +0000, Geoffrey Carman wrote:


>>
>> Nice articles.

>
> Glad to help, send fish. I love herring. (Someone actually mailed me
> herring!!)
>
>> I got it working now.
>> Thank you very much.

>
> What specifically did you do to fix it? (For the record, and the next
> person with the same issue and finds this in Google).


1) Read the articles, and basked in the fountains of knowledge
2) Figured, that since it was supposed to work like described, I had to be
in err
3) Found the typo and fixed it.

0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing the URL of an integration activity

On 12/17/2015 12:42 PM, Nicolai Jensen wrote:
> On Thu, 17 Dec 2015 16:39:22 +0000, Geoffrey Carman wrote:
>
>
>>>
>>> Nice articles.

>>
>> Glad to help, send fish. I love herring. (Someone actually mailed me
>> herring!!)
>>
>>> I got it working now.
>>> Thank you very much.

>>
>> What specifically did you do to fix it? (For the record, and the next
>> person with the same issue and finds this in Google).

>
> 1) Read the articles, and basked in the fountains of knowledge
> 2) Figured, that since it was supposed to work like described, I had to be
> in err
> 3) Found the typo and fixed it.


PEBKAC? Or loose nut behind the keyboard? 🙂

My favorite, was mistyping the MSG driver DN in the DCS driver config
and using it to expose two different bugs in DCS/Reporting. 🙂


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.