This topic applies only to the IBM Business Process Manager Advanced configuration.

Installing on Citrix Presentation Server

You can install and run IBM® Integration Designer on a Citrix Presentation Server so that multiple users can then connect remotely from their Citrix Presentation Server clients.

About this task

Follow these instructions to install IBM Integration Designer to run on Citrix Presentation Server.
Note: Throughout this text, the terms "installer" and "product installer" refer to the user ID that installed IBM Integration Designer.

Procedure

  1. When you install IBM Integration Designer on the server, ensure that you are logged on as a user with administrator access.
  2. After installing, ensure that the installation directory is read-only. This is the product directory, not the shared install directory. This step will ensure that the configuration information is written in the home directory. If this measure is not taken, all users will end up using the same location for their configuration area, which is not supported.
    Note: Ensure that client users are granted write permission to the following directory, or the integrated test environment server status cannot be detected:install_root\runtimes\bi_version_stub\
  3. When launching IBM Integration Designer from a client, the workspace is created in a directory specified by the user.
  4. In order to use the servers in the test environment, a profile is required for each nonroot user. The product installer can grant write permission to the appropriate IBM Business Process Manager files and directories to other nonroot users. The nonroot users can then create profiles. Alternatively, the product installer can create a group for users who are authorized to create profiles or give individual users the authority to create profiles. The following example task shows how to create a group that is authorized to create profiles.
Parent topic: Installing, upgrading, and uninstalling IBM Integration Designer

Configuring the Citrix Presentation Server

About this task

The installer can perform the following steps to create the "profilers" group and give the group appropriate permissions to create a profile.

Procedure

  1. Log on to the IBM Integration Designer system as the product installer (the product installer can be a root/Administrator or nonroot user).
  2. Using operating system commands, do the following tasks:
    1. Create a group named "profilers", which will contain all users who can create profiles.
    2. Create a user named user1, who can create profiles.
    3. Add users product_installer and user1 to the profilers group.
  3. For LinuxFor Unix Log off and log back on as the installer to pick up the new group.
  4. As the product installer, use operating system tools to change directory and file permissions.
    1. For LinuxFor Unix The following example assumes that the variable $WASHOME is the IBM Business Process Manager root_installation_directoryopt/ibm/BPM/v8.5 
      export WASHOME=opt/ibm/BPM/v8.5
echo $WASHOME
echo "Performing chggrp/chmod per WAS directions..."
chgrp profilers $WASHOME/logs/manageprofiles
chmod g+wr  $WASHOME/logs/manageprofiles
chgrp profilers $WASHOME/properties
chmod g+wr  $WASHOME/properties
chgrp profilers $WASHOME/properties/fsdb
chmod g+wr  $WASHOME/properties/fsdb
chgrp profilers $WASHOME/properties/profileRegistry.xml
chmod g+wr  $WASHOME/properties/profileRegistry.xml
chgrp -R profilers $WASHOME/profileTemplates
    2. For HP-UX Issue the following additional command where profile_template_name is default, dmgr, or managed: 
      chmod -R g+wr $WASHOME/profileTemplates/profile_template_name/documents
      The ownership of files is preserved when the files are copied to the profile directory during profile creation. You granted write permission to the profile directory so that files copied to the profile directory can be modified as part of the profile creation process. Files that are already in the profileTemplate directory structure before the start of profile creation are not modified during profile creation.
    3. For Linux Issue the following additional commands: 
      chgrp profilers $WASHOME/properties/Profiles.menu
chmod  g+wr $WASHOME/properties/Profiles.menu
    4. For Windows The following example assumes that the variable $WASHOME is the IBM Business Process Manager root installation directory C:\IBM\ProcServer\v8.5. Follow instructions in the Windows documentation to give the profilers group read and write permission to the following directories and their files: 
      @WASHOME\logs\manageprofiles
@WASHOME\properties
@WASHOME\properties\fsdb
@WASHOME\properties\profileRegistry.xml
      You might have to change the permissions on additional files if the non administrative user encounters permission errors. For example, if the product installer authorizes a non administrative user to delete a profile, then product installer might have to delete the following file:
    5. For LinuxFor Unix 
      install_root/properties/profileRegistry.xml_LOCK
    6. For Windows 
      install_root\properties\profileRegistry.xml_LOCK
      Give write access to the nonroot user for the file to authorize the user to delete the file. If the nonroot user still cannot delete the profile, then the product installer can delete the profile.

Results

The installer created the profilers group and gave the group proper permissions to certain directories and files to create profiles. These directories and files are the only ones in the installation root of IBM Integration Designer to which a nonroot user needs to write to create profiles.