- Stop the WebSphere Portal server.
- Backup the following files: wkplc.properties and wkplc_comp.properties files in the wp_profile_root/ConfigEngine/properties directory
- Edit the values in the properties file, wkplc.properties file and enter the appropriate value for your environment in the WpsContextRoot.
- Edit the values in the properties file, wkplc_comp.properties file and enter the appropriate value for your environment in the following properties: WsrpContextRoot, WpsPersonalizedHome, & WpsDefaultHome.
WpsPersonalizeHome=myapps
WpsDefaultHome=apps
- Save and close.
- Navigate to wp_profile_root/ConfigEngine/
- Restart WebSphere_Portal
# ./ConfigEngine.sh modify-servlet-path-portlets -DPortalAdminPwd=<*****> -DWasPassword=<****>
- Restart WebSphere_Portal
- Testing after script run successfully. Open browser and go to :
- If have successfully configured the portal, it should come back with a login page.
Note: The modify-servlet-path only modifies the Portal enterprise applications with the new context root. If you have a business requirement to have a consistent context root, including when portlets load, run the modify-servlet-path-portlets task as well. The modify-servlet-path-portlets task modifies the PA_* applications.
Problems and Resolutions:
Error 400: EJPEC0903E: The computation of the VP Login redirect URL failed.
Error 400: EJPSD0020E: The WAS request URL cookie was not found. Either cookies are not enabled in the used browser or the Servlet is being directly accessed.
Resolution: Stop node, syncNode.sh to deployment manager, and startNode.sh
Login to the deployment manager, navigate to Resources > Resource Environment Providers > WP_ConfigService
Add or edit the following properties:
uri.context.path = appschic
uri.home.public = apps
uri.home.protected = myapps
uri.context.path.facade = mywsrp
No comments:
Post a Comment