How to cluster user creation in IS 61

[machadowl]

The user creation process in webMethods (file "user.cnf") is not clustered, what means that each user created in either app #1 or app #2 is not automatically synchronized across the clustered servers. The answer from webMethods is very clear: we should either use LDAP or NIS (formerly known as Yellow Pages in Unix), but I need a less cumbersome solution other than having to maintain a directory server besides the webMethods IS server.

Question 1: does anybody tried to automate the user creation before and had a solution to effectivelly cluster file "users.cnf"? How?

Question 2: I have thought of creating users using Trading Networks repository by creating new TN Profiles for each new user needed in the system via TN's APIs as an alternative. There is a non-documented service called "wm.tn.access:createPartnerAccount" in package WmTN but I am not sure if this would solve my problem. Does anybody know if there is any API that could be used to programmatically create new Trading Partners in TN effectivelly (and consequently it will create new users in IS)?

Your help is greatly appreciated.

Thanks in advance!

[machadowl]

Just in case someone else needs a helping hand like I did...

Here is the scoop. Using the NFS or any file sharing mechanism will NOT help at all. webMethods keeps objects in memory and after the file user.cnf is updated in both server there is the need to update the server memory as well with the new configuration. This is not a practical approach.

The solution we found was to create a remove server alias (webMethods Admin page: Settings > Remote Servers) and create a link between the two clustered servers, and I also had to modify the code to introduce two extra steps:

1. Create the user locally in the server by using the API "wm.server.access:userUpdate"
Note: this API is one of those interesting APIs that you will NEVER find in any webMethods documentation and they don't like that idea of us using it, but it works.

2.Using the pub.remote:invoke service we could execute (run) the API "wm.server.access:userUpdate" in the other clustered server and we were able to create the same user in the second clustered server as well.

This was it...

Case closed!