Question & Answer
Question
How can I change the drive or path of the Reporting workspace directory to a different location than where Information Server creates it by default?
Cause
The Information Server Reporting workspace is used at run time for holding temporary status and information related to report generation. The amount of space required varies depending on the number, types and complexity of reports created. In some cases, the default location of the Reporting workspace does not have adequate space so it may be necessary to relocate to a different location. When the workspace is located in a tmp directory location, it could potentially be vulnerable to being deleted or files removed as part of some system administrator or user maintenance activity. To avoid this problem you may wish to change the default reporting workspace to a different directory.
Answer
The default reporting workspace location is different for various releases of InfoSphere Information Server.
Note: <temp> is /tmp or /var/tmp on Linux/Unix/AIX and %temp% on Windows.
By default the reporting workspace location for version 8.0 is:
<temp>/WDISuite/Reporting/
By default the reporting workspace location for version 8.1 is:
/IBM/InformationServer/ASBServer/apps/Reporting/
By default the reporting workspace location for versions 8.5, 8.7, 9.1.x, and 11.3.x running WebSphere Application Server Network Deployment is:
<temp>/informationServer/Reporting<Machine-Name><Node-Name><Server-Name>/
eg. /tmp/informationServer/ReportinghostnameNode01server1/
In a Network Deployment clustered configuration, a workspace is created on each system hosting a
managed node of the cluster for each cluster member on those systems.
By default the reporting workspace location for version 11.3.x running WebSphere Application Server Liberty profile is:
<temp>/informationServer/Reporting<host><iis.server.uid>
where <iis.server.uid> is the value for iis.server.uid in the <IIS_Home>/wlp/usr/servers/iis/folder/bootstrap.properties file. For example:
iis.server.uid=e1a45178
You can change the default location, if desired.
To force the creation of the reporting workspace to a specific location, please follow these steps
For a stand alone Non-clustered WebSphere Application Server Network Deployment configuration:
1. Log in to the WebSphere Application Server administrative console with administrator privileges.
2. Navigate to the Java Virtual Machine settings: Servers->Application Servers->server1->Java and Process Management->Process Definition->Java Virtual Machine.
3. Find the Generic JVM Arguments options and add the following to the JVM arguments list:
-Dinfoserver.reporting.workspace=path
where path is the full directory path to where you wish the reporting workspace directory to be created.
eg. -Dinfoserver.reporting.workspace=/tmp/reporting
Note: Add a space between this and any other existing entries in this field. Do not put a space between the -D and infoserver. The directories do not need to exist. They will be created if not found. If any directory in the path contains a space, then the full path must be included in single quotes. Do not use double quotes.
4. Click apply, then click on the link "save" to change directly to the master configuration.
5. Stop and re-start WAS properly.
After re-starting WAS, look at the specified location to confirm the workspace directories were created there.
For a clustered WebSphere Application Server Network Deployment configuration:
1. Log in to the WebSphere Application Server administrative console with administrator privileges.
2. Navigate to Servers -> Server Types -> WebSphere application servers and then
click on an application server from the list of servers in the cluster. Under Server Infrastructure, expand Java and Process Management and select Process definition. Select Java Virtual Machine.
3. Add the following under the Generic JVM arguments:
-Dinfoserver.reporting.workspace=path
where path is the full directory path to where you wish the reporting workspace directory to be created.
Note: Add a space between this and any other existing entries in this field. Do not put a space between the -D and infoserver. The directories do not need to exist. They will be created if not found. If any directory in the path contains a space, then the full path must be included in single quotes. Do not use double quotes.
4. Click OK.
At the top of that page where you see
Application servers > servername > Process definition
select Application servers and then make the same changes to the remaining cluster member's application servers whose workspace you wish to relocate. When finished changing all application servers, click Save at the top of the screen.
5. Restart the cluster.
After re-starting the cluster, look at the specified locations on each managed node to confirm the workspace directories were created there.
For WebSphere Application Server Liberty Profile:
1. Stop the server.
Unix: <IS_Home>/ASBServer/bin/MetatadataServer.sh stop
Windows: net stop infosvr
2. Navigate to <IS_Home>/wlp/usr/servers/iis/ and open the file jvm.options file.
3. Make an JVM entry -Dinfoserver.reporting.workspace at the end of this file pointing to the new reporting workspace location.
e.g:
-Dinfoserver.reporting.workspace=/tmp/newReportingWorkspace
4. Start the server
Unix: <IS_Home>/ASBServer/bin/MetatadataServer.sh run
Windows: net start infosvr
5. Doing so, the new reporting workspace using the format, Reporting<host><iis.server.uid>, would be created under the location specified in step 3.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21317914