The manageprofile command fails in shared memory configurations

Resolving The Problem

To resolve this problem, complete the following steps:

1. Change the value of the OSGI_CFG variable in the app_server_root/bin/setupCmdLine.sh or app_server_root/bin/setupCmdLine.bat file to reference an existing location with write permission.
   
   For example in the setupCmdLine.sh file:
   OSGI_CFG="-Dosgi.configuration.area=/writeableWorkspace/configuration"
   
   For example, in the setupCmdLine.bat file:
   SET OSGI_CFG=-Dosgi.configuration.area=d:\writeableWorkspace\configuration
   
   
2. Add following line of code to the app_server_root/bin/manageprofiles.sh or app_server_root/bin/manageprofiles.bat file:
   
   "$OSGI_INSTALL" "$OSGI_CFG" \
   
   
• In the manageprofiles.sh file, the line of code must be added after the following line:
  
  $JVM_EXTRA_CMD_ARGS \
  
  The updated manageprofiles.sh file then contains the following code:
  

${JAVA_EXE} \
$JVM_EXTRA_CMD_ARGS \
"$OSGI_INSTALL" "$OSGI_CFG" \
-DWAS_HOME=${WAS_HOME} \
-Dwas.install.root=${WAS_HOME} \
-classpath ${WAS_CLASSPATH} \
-Dws.ext.dirs=${WAS_EXT_DIRS} \
com.ibm.wsspi.bootstrap.WSPreLauncher \
-debug -nosplash -application \
com.ibm.ws.bootstrap.WSLauncher \
com.ibm.ws.runtime.WsProfile \"$@"


• In the manageprofiles.bat file, the line of code must be added after the following parameter:
  
  "-Dwas.install.root=%WAS_HOME%"


The updated manageprofiles.bat file then contains the following code on one continuous line:

%JAVA_EXE% -Xms256M -Xmx256M -Xquickstart "-DWAS_HOME=%WAS_HOME%" "-Dwas.install.root=%WAS_HOME%" %OSGI_CFG% %OSGI_INSTALL% -classpath "%WAS_CLASSPATH%" "-Dws.ext.dirs=%WAS_EXT_DIRS%" com.ibm.wsspi.bootstrap.WSPreLauncher -nosplash -application com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsProfile %*