HP: Configuring developer mode
Use developer mode to improve startup performance, and to configure IBM WebSphere Portal for development. Developer mode is for a development environment only. Do not use the developer mode in a production environment. We can also run the optimize-derby-database task to improve the Derby database performance.
Install WebSphere Portal.
This task modifies the following components:
- JVM
- The JVM is switched to development mode. This setting is a WebSphere Application Server specific setting independent of WebSphere Portal. The initial heap size is set to 768 MB to reduce the amount of garbage collection during startup.
- Portlets
- Portlets and web applications are activated on first access and not at the startup. However, some of the portlets and applications are required at startup. Create a white list, which contains the list of applications required at startup.
To add applications to the white list, modify...
WP_PROFILE/PortalServer/config/StartupPerformance/wp.base_TargetMapExclList.properties
Add a line such as App_name, where App_name is the name of the application. To get a list of available applications...
Applications - Application Types - WebSphere enterprise applications
- Open a command prompt.
- Stop the WebSphere_Portal server..
- Change to the WP_PROFILE/ConfigEngine.
- Run the ./ConfigEngine.sh optimize-derby-database task to improve the performance of the Derby database.
This task is appropriate only in a demonstration or development environment that is not configured to use WCM. We can also run the optimize-derby-database task after large data changes in the database.
- Start the WebSphere_Portal server.
- Run...
ConfigEngine.sh enable-develop-mode-startup-performance
- Restart the WebSphere_Portal server to propagate the change.
- Prepare the remote web server for the developer mode.
What to do next
To revert to a production server.
./ConfigEngine.sh disable-develop-mode-startup-performance -DWasPassword=foo task
Then, stop and restart the WebSphere_Portal server to propagate the change.
We can run the disable-develop-mode-startup-performance task for the following scenarios:
- When we are done developing the portal and portlets.
- If the development settings are not adequate for a special development situation.
- When we cannot re-create a problem on the development server.
Parent Change to developer modeRelated tasks:
Application server settings