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.
Highlighted
fartyalvikram Contributor.
Contributor.
872 views

The URI of the workflow server has not been configured

I am using iManager 3.0.0 which is installed on Red Hat Enterprise Linux Server release 6.8.
My eDirectory version is NetIQ eDirectory 8.8 SP8 v20811.09.
I have User Application which is installed using Identity_Manager_4.5 on Red Hat Enterprise Linux Server release 6.8.
I am trying to see Workflow server URI using below steps
Step 1 : Open iManager, Go to Workflows task.
Step 2 : Select User Application Driver in User Application driver field then click OK.
when I select the User Application driver it gives an alert with the following message
The URI of the workflow server has not been configured for the selected driver.
We have two User Application Server, So I have configured inside Driver Parameters, User Application VIP on User Application Driver.
I also try to configured User Application server IP and port inside Driver Parameters but it gives the same alert message.
Labels (1)
0 Likes
7 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: The URI of the workflow server has not been configured

Care to post your use application driver config somewhere for review?

Also I presume you have at least two servers, one with iManager and the
other with eDirectory and IDM, as you MUST NOT have iManager 3.x on an
eDirectory 8.x server or you will likely break eDirectory.

It may help to explain why you have two UserApp driver configs in one
environment. I presume this is for an upgrade, and I think you had a
thread mentioning that in another forum that I cannot find right now, but
those details may help find a better approach overall. Normally two
UserApp driver configs is not supported as I recall.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
fartyalvikram Contributor.
Contributor.

Re: The URI of the workflow server has not been configured

Now I can able to see Workflow server URI the reason is that my one replica server is down at that time when I up this server it showing me Workflow server URI,
But when I select Workflow server URI and my user uaadmin is automatically retrieved then I enter the password and hit Login.
After click on Login button they gives the following error
Workflow server URI
Workflow - Error 
The following Workflow administration exception occurred: Connection timed out

I have two User Application Server but I am using my User Application F5 VIP address in Driver Parameter in User Application driver.
0 Likes
fartyalvikram Contributor.
Contributor.

Re: The URI of the workflow server has not been configured

I have two eDirectory Server (192.168.1.121/122) one is master and second one is replica and two User Application Server (192.168.1.111/112).
My iManager is installed on Master eDirectory server.
Inside User Application Driver, in Driver Configuration tab I have configured Driver Parameters Host for "192.168.1.121" instance is "192.168.1.111" and for "192.168.1.122" instance is "192.168.1.112"
When every server is UP, inside iManager I can see "Workflow server URI" Workflow section using is below values
http://192.168.1.111:8180/IDMProv
http://192.168.1.112:8180/IDMProv
When I stop replica eDirectory (192.168.1.122) and Master eDirectory (192.168.1.121) is running then I can see only http://192.168.1.111:8180/IDMProv value inside "Workflow server URI" on iManager.
But when I stop Master eDirectory (192.168.1.121) and replica eDirectory (192.168.1.122) is running then inside "Workflow server URI" there is no value is showing on iManager.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: The URI of the workflow server has not been configured

Some attributes are defined as "Per-Replica', meaning they are not
replicated from one server to another. Identity Manager (IDM) uses these
types of attributes in order to allow configuration of driver
configuration objects differently on different eDirectory servers, which
is a valid use case for various reasons. It sounds like this particular
driver config is meant to work on the Master, and not the Read/Write
replica, so you can use either Designer or iManager to move the
configuration over, but you should not do so without understanding the
implications. In your case it is probably fine, but in other cases it may
be a bad move.

In iManager there is a drop-down with the server name; you can change this
to show other servers listed in the DriverSet and set configuration
options differently per-server.

In Designer (preferred usually) you can do the same within the driver
object's properites. A drop-down at the top of each tab's contents shows
which server's information you are viewing.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
fartyalvikram Contributor.
Contributor.

Re: The URI of the workflow server has not been configured

In iManager I already configured the User Application URL inside Driver Parameter in User Application Driver for both instance means using the drop-down of eDir server one and the other.
Do I need to try this from the designer to change these Driver Config for User App URL and deploy this?

Some attributes are defined as "Per-Replica", is that attributes are used to retrieving the Workflow server URI in iManager? And can we verify these attributes in all replicas?
Do I need to Sync all replica using DSRepair?
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: The URI of the workflow server has not been configured

On 02/07/2018 10:14 AM, fartyalvikram wrote:
>
> *Some attributes are defined as "Per-Replica"*, is that attributes are
> used to retrieving the Workflow server URI in iManager? And can we


Probably; driver configuration data are some of the most-used ones.

> verify these attributes in all replicas?
> Do I need to Sync all replica using DSRepair?


No, your system should only be pointing to the server with the correct
attributes, the one running the UserApp driver, so there is no need o
update other replicas, assuming you even bother to link a DriverSet to
multiple servers, which I would not generally recommend.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
Knowledge Partner
Knowledge Partner

Re: The URI of the workflow server has not been configured


> *Some attributes are defined as "Per-Replica"*, is that attributes are
> used to retrieving the Workflow server URI in iManager? And can we
> verify these attributes in all replicas?
> Do I need to Sync all replica using DSRepair?


The Per-Replica flag in eDir schema is sort of funny. eDir is after a
replicated distributed database. So why would you flag something,
per-replica or put another way, do not sync?

That is, you have three replicas in the ring. The object
ou=Test,ou=Apps,o=acme has an attribute DirXMl-ConfigInfo, why would you
want the version on Server1 to hold the value "Testing", on Server2 to
say "Not Testing", and on Server3 "Testing? We don't need testing where
we are going!".

Seems kind of strange, and implies an inconsistent database. Except when
of course, you really want it.

Imagine you have IDM installed on two of those servers in the replica
ring and mean for them to provide manual failover support.

I.e. If Server1 goes down, you could manually disable the drivers on
Server1, and enable/start them on server2.

But Server2 might be in a datacenter, elsehwere from Server 1 (if you
are actually planning DR, might seem wise) and in fact you may have a
different connection endpoint for each driver in data center 2.

Therefore the DirXML-ConfigInfo style attribute that stores the connect
string should hold a different value on Server1 than on Server2 by
design, and not replicate (since they would overwrite each other).

This saves us from otehr more complex methods to handle multiple nodes,
and is an elegant use of a schema feature that I am pretty sure predates
IDM.



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.