Configuration Wizard Profile (cw_profile) - Enable Standalone LDAP using configuration wizard workflows


Recently came across one usecase where configuration wizard profile is very useful to configure multiple development workstations.

The Configuration wizard is installed on server1 in the cw_profile (WebSphere/AppServer/profiles/cw_profile) profile  .

NOTE : You can find the wizard.war file under /Websphere/ConfigEngine/installableApps)

  1. Accessing configuration wizard

you can start the cw_profile from /WebSphere/AppServer/profiles/cw_profile/bin/

or you can access configuration wizard profile is using first steps





Once we start the configuration wizard profile, you can see the "Configuration Wizard" option in admin console as below (https://sivapc.sivavaka.com:9044/ibm/console/)



  1. Existing sample workflows


  1. UseCase:  - Configuring the Standalone LDAP

Customizing workflow (based on your environment)
Following shows how to customize the "configuring the standalone LDAP security"







##############################################################################
# IBM WebSphere Portal configuration helper file for script EnableLDAPSecurity.
##############################################################################
standalone.ldap.baseDN=dc=sivavaka, dc=com
standalone.ldap.bindDN=cn=wasadmin,ou=system,dc=sivavaka,dc=com
standalone.ldap.bindPassword=wasadmin
standalone.ldap.et.group.objectClasses=groupOfUniqueNames
standalone.ldap.et.group.objectClassesForCreate=
standalone.ldap.et.group.searchBases=ou=groups,dc=sivavaka,dc=com
standalone.ldap.et.personaccount.objectClasses=inetorgperson
standalone.ldap.et.personaccount.searchBases=ou=persons,dc=sivavaka,dc=com
standalone.ldap.gm.dummyMember=uid=dummy
standalone.ldap.gm.groupMemberName=uniqueMember
standalone.ldap.gm.objectClass=groupOfUniqueNames
standalone.ldap.gm.scope=direct
standalone.ldap.groupFilter=(&(cn=%v)(|(objectclass=groupofUniqueNames)(objectclass=accessGroup))
standalone.ldap.groupIdMap=*:cn
standalone.ldap.groupMemberIdMap=
standalone.ldap.groupParent=ou=groups,dc=sivavaka,dc=com
standalone.ldap.groupRdnProperties=cn
standalone.ldap.host=ldap.sivavaka.com
standalone.ldap.ldapServerType=IDS
standalone.ldap.personAccountParent=ou=persons,dc=sivavaka,dc=com
standalone.ldap.personAccountRdnProperties=uid
standalone.ldap.port=636
standalone.ldap.primaryAdminId=uid=wpsadmin,ou=persons,dc=sivavaka,dc=com
standalone.ldap.primaryAdminPassword=wpsadmin
standalone.ldap.primaryPortalAdminGroup=cn=wpsadmins,ou=groups,dc=sivavaka,dc=com
standalone.ldap.primaryPortalAdminId=uid=wpsadmin,ou=persons,dc=sivavaka,dc=com
standalone.ldap.primaryPortalAdminPassword=wpsadmin
standalone.ldap.realm=SivaRealm
standalone.ldap.serverId=cn=wasadmin,ou=system,dc=sivavaka,dc=com
standalone.ldap.serverPassword=wasadmin
standalone.ldap.userFilter=(&(|(uid=%v)(cn=%v))(|(objectclass=accessGroup))
standalone.ldap.userIdMap=*:uid
WasPassword=wasadmin







 Click on Next ( If you want to save changes to local directly, you can save in above step).




  1. Executing the Scripts that’s generated as part of custom workflow

Instruction file (html) named after your workflow
The instruction file provides you with tailored steps for your configuration and your target operating system. Based on the information provided when customizing your workflow, an instruction file is created to guide you in running scripts in combination with other manual configuration steps for your specific configuration goal.
Scripts
Depending on the conditions of your environment, the script files use a .sh or .bat file extension or are simple text files. Use the scripts, along with other manual configuration steps described by your instruction file, to perform your configuration. For example, your workflow may provide you with a script to run a ConfigEngine task rather than you running the task.
Updated properties
Configuration helper files with updated property values entered for your configuration are created when customizing your workflow. You can use these helper files to save time later.
.wfi file
File used for troubleshooting your workflow.

Instructions HTML looks like below.

NOTE : In Websphere Portal 8.5, you can Install the PAA (Portal Application Archive) files also

Resources:

WebSphere Portal v8.5 : Removed/Depreciated features

Recently I was going through the list of features thats going to deprecate in upcoming websphere portal i.e. WP v8.5

1.     Features no longer supported

a.      Removed theme

The Portal 6.1.x themes, which includes Portal, PortalWeb2, and Tab Menu - Page Builder were removed. These themes migrate as is to WebSphere Portal 8.5, but they will no longer work and are no longer supported. You must manually update 6.1.x themes by merging their functionality into a clean copy of a Portal 8.5 theme on the target server.


2.     Deprecated features

a.      Shared Pages

Shared pages have been deprecated.

b.     Enabler Component

The Enabler component has been deprecated.

c.      LikeMinds and Feedback

The LikeMinds and Feedback database domains have been deprecated.

d.     Stand-alone LDAP user registry

The stand-alone LDAP user registry configuration is deprecated. Instead, configure the federated LDAP user registry. If you are migrating from WebSphere Portal Version 7.0 or 8.0 with a stand-alone LDAP user registry, you can continue to use your stand-alone LDAP user registry. However, you should run the wp-modify-federated-security to change to a federated LDAP user registry.

e.     Active Credentials

Active credentials are deprecated from the Credential Vault portlet. Passive credentials are still available.

f.       Parallel Portlet rendering

The Parallel Portlet rendering feature has been deprecated.

g.      Web Clipper

The Web Clipper portlet has been deprecated. Use the Virtual Web Application Manager portlet instead.


h.     Mashups Enabler API

The Mashups Enabler API has been deprecated.

i.       LTPA version 1 token

The LTPA version 1 token has been deprecated. WebSphere Application Server Version 8.5.5. disables the LTPA version 1 token by default. If you are integrating with third-party applications that rely on LTPA version 1, update the application to support LTPA version 2. If you cannot update the application, you must manually re-enable LTPA version 1 support after you complete the migration.

j.       Remote Rendering Portlet

The remote rendering portlet is now deprecated. The Web Content Viewer (JSR 286) portlet should be used instead.

k.      Web2Bookmarks portlet

The Web2Bookmarks portlet is no longer available for immediate use. Instead, download the portlet from the IBM WebSphere Portal Business Solutions Catalog.

l.       Deprecated Theme


The WebSphere Portal Page Builder 7.x theme was deprecated.



WebSphere Portal v8.5 : What’s New


Recently was looking at the upcoming Websphere Portal v8.5 features , some of major features introduced are as below

a.      Installation/Migration using Configuration Wizard


b.     Remote Search Configuration using Installation manager


c.      Create single PAA file for delta change releases


d.     WAB(web application bridge) : create preconfigured web dock portlets

Once the web dock portlets are configured it is easy to add the portlets

e.     Information Mode

Information mode displays more inline information.

f.       Ajax proxy configuration service (out bound http connections)

Instead of placing proxy-config.xml under WEB-INF/ directory , we can configure like a standard datastore-like configuration.

g.      Theme optimization analyzer


h.     Configuration wizard to deploy the PAA files


i.       Attribute based security in WCM

You can extend the access control permission checks for Web Content Manager content beyond the user or group-based decisions.

j.       Social rendering list templates

Easy to bring the connections data into portals

k.      Item syndication status

Users can determine whether an item is synchronized between the syndicator and subscriber, pending syndication, failed, or configured to be syndicated.