Troubleshoot: Create a WebSphere Portal profile
View troubleshoot information for creating a WebSphere Portal profile.
Each potential step in the configuration is included. Since the steps vary, depending on the selections, the steps are not numbered. Find the step that failed to learn more about correcting and recovering from the failure. To change a value entered in the wizard, then run the configuration again.
If we must go through the wizard again, download the wizard selections that you made to save time. Then, cancel the configuration. Start the process over and upload the saved selections. Correct or enter values for the parameters that caused the failure.
Create the target profile for WebSphere Portal in the WAS
If the step fails, see the logs for the manageprofiles command to determine why the step failed. The wizard uses the portal profile templates to create the deployment manager profile. An error might result from a problem with the profile templates. The error message in the log provides more information.
The log files are in...
app_server_root/logs/manageprofiles
the target profile for WebSphere Portal in the WebSphere Application
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step if an unrecoverable error occurs If an unrecoverable error occurs and this step fails, remove the profile. Use the manageprofiles command to remove the profile.
The command file is in the app_server_root/bin directory. The command file is a script named manageprofiles.sh|bat.
Example:
/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -delete -profileName dmgr01
Delete the profile directory only if the manageprofiles command completes successfully.
Then, run Create the target profile for WebSphere Portal again.
Install the ConfigEngine into the target WebSphere Portal profile
If we completed a binary installation, this is the first step.
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step If this step fails, look in configtrace.log for any failures.
Register the WebSphere Portal components with the ConfigEngine
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again provided you keep the same profile name. Clean up step If this step fails, look in configtrace.log for any failures.
Consolidate the properties files for WebSphere Portal components used in this configuration into a single properties file
step: Consolidate the properties files for WebSphere Portal components used in this
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step If this step fails, look in configtrace.log for any failures.
Prepare the profile for basic configuration
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step If this step fails, look in configtrace.log for any failures.
Validate the database connection and environment
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step Contact support.
Deploy applications into the portal profile
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step If this step fails, look in configtrace.log for any failures.
Configure the JCR, theme, and core runtime components of the portal server
step: Configure the JCR theme, and core runtime components of your
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step If this step fails, look in configtrace.log for any failures.
Deploy the administration portlets and pages to the portal
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step If this step fails, look in configtrace.log for any failures.
Deploy the out-of-box pages and portlets to the portal
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step If this step fails, look in configtrace.log for any failures.
Remove the application server (server1) from the profile
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If we already removed server1, we do not need to run this step again. Clean up step If this step fails, look in configtrace.log for any failures.
Stop the portal server
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step Do not skip this step, if we are running the configuration again. Clean up step Check for failures in the systemout and systemerror logs for starting or stopping the portal server.
Collect the deployment manager augmentation files and profile templates required to build a cell
step: Collect the deployment manager augmentation files and profile
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step If this step was successful, we can skip it if we run the configuration process again. Clean up step If this step fails, look in configtrace.log for any failures.
Restart the WebSphere Portal server
step: Restart the WebSphere Portal
Actions Notes Run the step again If this step fails, we can run this step again after you clean up the issue. Skip the step Do not skip this step, if we are running the configuration again. Clean up step Check for failures in the systemout and systemerror logs for starting or stopping the portal server.