Installing the default Process Portal space on z/OS

In most operating systems, the default Process Portal space is installed automatically. However, for z/OS systems that are using the local OS user registry and SAF authorization, you must complete additional steps to install the default space.

About this task

The Business Space component uses the primary administrative user name for setting the administrator for the welcome space. However, on z/OS there is no concept of primary administrator when using the local OS user registry and SAF authorization. This means that you must provide a valid ID in the registry to install the default space.

Procedure

Complete the following steps for a stand-alone server:
1. Modify the MashupAdminForOOBSpace property in the configuration file profile_root/BusinessSpace/node_name/server_name/mm.runtime.prof/config/ConfigService.properties with a valid user ID.
2. Run the command updatePropertyConfig in the wsadmin environment of the profile:
  - Jython example:
```
AdminTask.updatePropertyConfig('{-serverName server_name -nodeName node_name -propertyFileName "profile_root/BusinessSpace/node_name/server_name/mm.runtime.prof/config/ConfigService.properties" -prefix "Mashups_"}') 
```
  - Jacl example:
```
$AdminTask updatePropertyConfig {-serverName server_name -nodeName node_name -propertyFileName "profile_root/BusinessSpace/node_name/server_name/mm.runtime.prof/config/ConfigService.properties" -prefix "Mashups_"} 
```
3. Save your changes to the master configuration using one of the following commands:
  - Jython example:
```
AdminConfig.save()
```
  - Jacl example:
```
$AdminConfig save
```
    .
4. In the profile where the server is located, open the profile_root/BusinessSpace/node_name/server_name/mm.runtime.prof/public/oobLoadedStatus.properties file and update the importSpaces.txt property:
```
importSpaces.txt=true
```
5. Restart the server.
Complete the following steps for a cluster:
1. Modify the MashupAdminForOOBSpace property in the configuration file deployment_manager_profile_root/BusinessSpace/cluster_name/mm.runtime.prof/config/ConfigService.properties with a valid user ID.
2. Run the command updatePropertyConfig in the wsadmin environment of the deployment manager profile:
  - Jython example:
```
AdminTask.updatePropertyConfig('{-clusterName cluster_name -propertyFileName "profile_root/BusinessSpace/cluster_name/mm.runtime.prof/config/ConfigService.properties" -prefix "Mashups_"}') 
```
  - Jacl example:
```
$AdminTask updatePropertyConfig {-clusterName cluster_name -propertyFileName "profile_root/BusinessSpace/cluster_name/mm.runtime.prof/config/ConfigService.properties" -prefix "Mashups_"} 
```
3. Save your changes to the master configuration using one of the following commands:
  - Jython example:
```
AdminConfig.save()
```
  - Jacl example:
```
$AdminConfig save
```
    .
4. Get the name of the cell, node, and server for the custom profile:
  1. In the deployment manager profile, open the deployment_manager_profile_root/BusinessSpace/cluster_name/mm.runtime.prof/config/ConfigService.properties file.
  2. Look for the name of the cell, node, and server in the com.ibm.mashups.directory.templates or com.ibm.mashups.directory.spaces properties.
  3. Use the name of the cell, node, and server to locate the custom profile.
5. In the custom profile, open the custom_profile_root/BusinessSpace/cluster_name/mm.runtime.prof/public/oobLoadedStatus.properties file and update the importSpaces.txt property:
```
importSpaces.txt=true
```
6. Resynchronize the custom profile:
  1. Open the administrative console and click System administration > Nodes.
  2. Click Full Resynchronize.
7. Restart the cluster.