1. We have found that one possible reason is missing jar files. The jar files required to get this to work correctly are listed herein. These jars are supposed to be under workpoint / lib folder:
2. To connect with EJB you will also need to make sure to have a correct JBoss application user in place:
In jboss/bin folder there is a batch file called add-user. Please run it and create a jboss application user.
Example: What type of user do you wish to add?
a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
Enter the details of the new user to add.
Realm (ApplicationRealm) :
Username : imuser
Note the name and password of the user you created.
When asked "Is this new user going to be used for one AS process to connect to another AS process?" Select No as the user information will be inserted in the Domain configuration instead of the standalone configuration.
Once you have created your user, open your workpoint-client.properties file (it is under \CA\Identity Manager\IAM Suite\IdentityManager\tools\Workpoint\conf):
Under the line: remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
add the following two lines:
Change the username and password to be what you entered when you created your user.
Note, for JBOSS 6.4, have to specifically change workpoint-client.properties to one of the following combinations:
For Wildfly, use remote.connection.default.port=8080.
No restart need on JBoss side – Designer should work now.