Frequently used websphere portal config engine tasks

Below are some of the most commonly used WebSphere Portal ConfigEngine tasks that you must know either you are playing a role of Portal developer or administrator.

start-portal-server

This task is used to Start the portal server. Before executing this task make sure that the portal admin user id and password should be set in wkplc.properties.


./ConfigEngine.sh start-portal-server

stop-portal-server

This task is used to Stop the portal server. Before executing this task make sure that the portal admin user id and password should be set in wkplc.properties.


./ConfigEngine.sh stop-portal-server

activate-portlets

In a clustered environment when the new portlet is deployed, WebSphere Portal cannot guarantee that the portlet has been successfully synchronized to each node in the cluster and thus cannot automatically activate the portlet during deployment.

In order to fix this issue, you have to run this task to activate the deployed portlets and to synchronize the changes across all cluster members.


ConfigEngine.bat activate-portlets -DWasPassword=password task from the wp_profile_rootConfigEngine directory

configure-wcm-authoring

This task installs the WCM Authoring Portlet, Local Rendering Portlet and Web Content Manager Portal pages on top of base portal installation.


ConfigEngine.bat configure-wcm-authoring -DPortalAdminPwd=xxx -DWasPassword=xxx

Note that if the WCM Authoring portlet is invisible after running this task, try going into Portal Admin > Web Modules and make sure the modules for WCM are started.

create-virtual-portal

Use this task to create a new virtual portal.


ConfigEngine.sh create-virtual-portal

Additional custom parameters can be passed to the task depending upon your requirement, so please refer to the Virtual portals reference for more details.

delete-virtual-portal

This task is used to delete a virtual portal by using its object ID. To determine the correct object ID of the virtual portal, use the task list-all-virtual-portals.

modify-virtual-portal Use this task to modify a virtual portal by using its object ID. To determine the correct object ID of the virtual portal, use the task list-all-virtual-portals.

list-all-virtual-portals

This tasks lists all your virtual portals, together with the information like title / description / realm and object ID of virtual portal:


./ConfigEngine.sh list-all-virtual-portals

export-library-copy

This task exports a copy of a web content library. Refer this article Exporting and importing a web content library copy for more details.

export-wcm-data

This task exports a web content library. Several things need to be in place for this task to be executed properly, so please refer this article Exporting and importing web content libraries for more details.

import-library-copy

This task imports a copy of a web content library. Refer this article Exporting and importing a web content library copy for more details.

import-wcm-data

This task imports a web content library. Several things need to be in place for this task to be executed properly, so please refer this article Exporting and importing web content libraries for more details.

list-server-ports

This task list and the available server ports.


ConfigEngine.bat list-server-ports -DWasPassword=password

list-server-ports-by-name

This task list all the server ports by their name.

ConfigEngine.bat list-server-ports-by-name -DServerName=server1 -DWasPassword=password

ConfigEngine.bat list-server-ports-by-name -DServerName=WebSphere_Portal -DWasPassword=password

modify-servlet-path

Changes the default portal Uniform Resource Identifier (URI) after installation.


./ConfigEngine.sh modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password

remove-wcm-authoring

This task uninstalls the WCM Authoring Portlet, Local Rendering Portlet and Web Content Manager Portal pages.

action-deploy-portlets-prereq.pzn

If you install Portal or WCM using the administration option, or base install, the Personalization features, including the Personalization Navigator and Personalization Editor, are not installed. However, you can add these features manually after installation by deploying the Personalization portlets and adding the Personalization Navigator and Personalization Editor to a page. This task deploys the personalization portlets.

UNIX:

./ConfigEngine.sh action-deploy-portlets-prereq.pzn -DPortalAdminPwd=<password> -DWasPassword=<password>

Windows:

ConfigEngine.bat action-deploy-portlets-prereq.pzn -DPortalAdminPwd=<password> -DWasPassword=<password>
Reference : https://wiki.base22.com/

No comments:

Post a Comment