Note: This is part of the $99.95 special deal as this course was released before December 2015. Have you ever wondered how to install and configure a federated repository (LDAP and internal file-based repository)? Have you ever had trouble creating a custom stand-alone LDAP configuration? Have you wondered how to automate the creation of a LDAP.. read more →

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Standalone LDAP What we will cover in the next few pages is how to configure WebSphere Application Server to use a standalone LDAP registry. The difference between a standalone LDAP repository and Federated Repositories is that the WAS administrative IDs and User ID’s are both referenced from the same LDAP server. If the LDAP service.. read more →

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Changing the OU for LDAP Bind What I would like to do now is take a walk through the Security – Users and Groups screens so we can see what they look like under Federated Repositories. Navigate to Users and Groups and select Manage Users We can see the following: As we can see above,.. read more →

Facebooktwittergoogle_plusredditpinterestlinkedinmail

 Adding LDAP to a federated repository We have covered how to install Apache DS, we will now look at adding LDAP to our Federated Repository. So far we have the internal fie-based registry names fileRegistry.xml, however our installed JEE application(s) will require a user registry. For this we want to use LDAP. We want to.. read more →

Facebooktwittergoogle_plusredditpinterestlinkedinmail

 Setting the internal Repository using Scripting Our federated repository is based on a virtual realm (A unique name defining the virtual registry as provided by the registries that are federated together and managed by the WebSphere Virtual Manager) The realm can consist of identities in: The file-based repository that is built into the system One.. read more →

Facebooktwittergoogle_plusredditpinterestlinkedinmail

When setting an LDAP repository in WebSphere Application WE get the following error: Validation failed: SECJ7716E: Primary administrative user Id does not exist in the registry.   When I click Set as current, I get the following error as seen in SystemError.log     Error [14/04/15 21:07:17:768 BST] 00000066 SystemErr R com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5020E Could not.. read more →

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Middleware Consulting & Architecture If you or your organisation require support in architecture, performance tuning, automation or simply advice, then please contact me via my support site and request a conversation, where we can discuss your requirement. About Steve Steve is a seasoned passionate technology professional, strategist and leader. An expert in technical communications, and adept.. read more →

Facebooktwittergoogle_plusredditpinterestlinkedinmail

This page is dedicated to creating a list of the typical tasks that a WebSphere Administrator is required to understand and be familiar in a typical work day. Feel free to comment and add you thoughts. Key concepts such as: Cell Node Profil JVM, JRE, Server, Stand alone Server, WASND (WebSphere Network Deployment) Clustering ,Clone.. read more →

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Question: There is a WAS environment configured with “Federated repositories”, e.g: LDAP registry and file registry, the “Primary administrative user” created in file registry. Recently there was a LDAP server down, at that time, All admin users could not login to Admin Console, even with “Primary Administrative User” which created in File Registry, this is definitely not.. read more →

Facebooktwittergoogle_plusredditpinterestlinkedinmail