Hello Experts,

I have created a new role and i would like to add that role to a ACL in Integration server, but when i try to search my newly created role
via ACLS-> ADD Users>

Hi,

please check if restarting the IS solves the issue.

The IS caches the informations from the directory.
This can take some time until the new informations make it to the cache.

Regards,
Holger

Hello Holger,

Thank for responding.

I did a bit of research and found that it is the caching as you mentioned.

This problem was solved by restarting the servers.

However i understood that every time you make a change to the role (add or delete user) it requires a restart.of the IS.

Regards,
Arun Chollety.

Hello Holger,

Thank for responding.

I did a bit of research and found that it is the caching as you mentioned.

This problem was solved by restarting the servers.

However i understood that every time you make a change to the role (add or delete user) it requires a restart.of the IS.

Regards,
Arun Chollety.

I think it’s not required. Please reload your monitor package alone and test once.

Regards,
Krishna

Hi Arun,

it is not really required to start the IS everytime.

Cache will expire at certain intervall and gets refreshed afterwards.

Regards,
Holger

Anyone knows how long the cache takes to expire? Three years later, we use version 10.1 and still hit this problem.

Typically, I add the new user and role in MWS. Then in IS, I define the new ACL and try adding the new MWS role to the ACL – this is when the problem occurs. I’ve tried waiting 10-20 minutes for the cache to expire (and the new role to appear in IS) – but without success. I end up restarting IS.

This is in my development environment though. New users/roles/ACLs are deployed using WmDeployer, so I wonder if this is solely a development issue (it’d be painful to restart production clusters on new role deployment).

I didn’t have this issue. After I create a role on MWS, I could immediately set a ACL for that role on IS. Did you try to hit the “Go” button to refresh role list?

Thanks @Xiaowei - yes, I did hit the ‘Go’ button (it’s a gotcha for sure).

Even waiting for an hour didn’t help - only an IS restart helps.

If you don’t mind, can you tell me your IS version and patches? I’m on IS 10.1 with IS_10.1_Core_Fix12,
Trading Networks Server 10.1 Fix 4 and IS_10.1_SPM_Fix3

I am on v9.9 without any patch.

You did configure Central User Management, right?

Thanks @Xiaowei - older may be better ! Yes, we do have Central users configured.

I have a blog here https://www.blogger.com/blogger.g?blogID=4200396608243839441to describe how to do central user management on IS. It contains some services to retrieve role list on MWS. Could you take a look and try it on your IS? To see if you could get the role list successfully?

Sorry, this is correct url Xiaowei's Blog: Enhanced Central User Management on webMethods

Hi,

In 10.1 there is a new IS fix which will solve this issue (it wasn’t present in 9.9).

Please update your installation with the latest fixes of all the products you have installed as there are dependencies between fixes (IS-MWS-UM… etc).

Best regards,

Thanks Gerardo - good tip! Frustrating as we just went live wtih 10.1. I’ll ask our implementation partner.

Let us know how it goes after the fix installation.

FYI - I am on 10.3 with the latest available fixes and I am able to see the Roles create on MWS immediately on IS. I assume you have selected the Provider=Central as in the screenshot attached.

IS_10.3_Core_Fix5
IS_10.3_SPM_Fix2
Trading Networks Server 10.3 Fix 1
Trading Networks Server 10.3 Fix 2
Trading Networks Server 10.3 Fix 3
MWS_10.3.0_Fix4

Thanks @Xiaowei – some ninja code there!

Thanks for the inputs @Mahesh. I plan to open an SI. SAG probably have a fix already ready for this

Hi,
Just one question… Do you have UM setup in IS?

Thanks

Can you check if the configuraiton of the Universal Messaging URL in the cluster.xml file

FYI, related fixes:

MWS-24425 (MWS_10.1_Fix8 )
My webMethods Server might fail to authenticate LDAP users although the users are valid and present in the LDAP directory.

The issue is resolved.

MWS-23569 (MWS_10.1_Fix7 )
When using a My webMethods Server cluster with Universal Messaging as the JMS provider, My webMethods Server might fail to synchronize role membership updates across the nodes of the
cluster. This issue occurs when updating the role membership of LDAP users.

The issue is resolved.

Your issue does not appear on 9.9 (I’ve tested).

Best regards,

@Gerardo - this is pertinent information on a silver platter. Thank you very much.

Our MWS patchlevel is MWS_10.1_Fix6. The problems you described for MWS_10.1_Fix7 and 8 come very close to describing our problem. We do use UM, and it was an LDAP user whose role was being adjusted. The only difference is I encountered this problem on a single node MWS (not a cluster), and between MWS and IS (not between nodes in an MWS cluster). But I have a sense IS is accessing old MWS role membership information, and these patches may fix the problem.

@Yogesh – yes, we have UM messaging as the default messaging for IS

@Mahesh – Thanks. I assume you mean this MWS file: /MWS/server/default/config/cluster.xml. It’s contents seems OK:

This is my complete xml where UM server is configured.

<?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?><Cluster clusterId="-1858469550" deploymentSymmetrical="false" distributedEventsEnabled="true" frontEndSecurePort="-1" frontEndUrl="http://localhost:8585" jndiProviderUrl="nsp://localhost:9000">
<!-- lists all physical servers in the cluster -->
<Category name="servers">
<Component class="com.webmethods.portal.system.cluster.impl.Server" enabled="true" name="Mahesh-PC-node60243" nodeType="MWS"><Properties host="localhost" name="http" port="8585"/><Properties host="localhost" name="https" port="0"/><Role name="autodeploy"/><Role name="search"/><Role name="taskengine"/><Role name="notification"/></Component></Category>
</Cluster>

If the file seems identical then the SAG patch fix should resolve your issue. Let us know how you go so it will be helpful to me and others.