Installing the InfoPrint Manager macOS X client

There are two versions of the InfoPrint Manager macOS X client: the previously existing non-LDAP macOS Command Line Client and the LDAP-enabled macOS Command Line Client. The LDAP-enabled macOS Command Line Client and the non-LDAP macOS Command Line Client are packaged in different pkg packages. The LDAP-enabled macOS Command Line Client requires LDAP authentication for job submission. You must authenticate with an LDAP server to execute job submissions from the macOS Command Line Client. If you install the LDAP version of the macOS Command Line Client and you want to switch back to the standard non-LDAP version, you can install it over the LDAP version. The installer allows you to install one version of the macOS Command Line Client over the other and automatically removes the old version.

The macOS Command Line Clients and the InfoPrint server are available in these languages:

  • English
  • French
  • German
  • Italian
  • Japanese
  • Spanish
To use a non-English version of InfoPrint Manager, your AIX system must have installed the file sets for that language. You should associate the macOS Command Line clients with an InfoPrint server running in your language.

To install the InfoPrint Manager macOS Command Line clients:

  1. Log onto the macOS system as root.
  2. Insert the InfoPrint Manager: Common Clients DVD-ROM, LCD4–5642 into your drive.
  3. Copy the installer package for the version of the macOS Command Line Client you want to install to a temporary location. For example: /tmp.
  4. To install the non-LDAP macOS Command Line Client, double-click on the ipr-cmd-4.9.m-n.i586.pkg package to launch the installer.

    To install the LDAP-enabled macOS Command Line Client, double-click on the ipr-cmd—ldap–4.9.m-n.i586.pkg package to launch the installer.

    Where m and n represent the service update level.

    If you want to install the macOS Command Line Clients in silent mode:

    1. Open a command terminal.
    2. Execute the following commands:
      sudo -S installer -verbose -pkg /tmp/ipr-cmd-4.9.m-n.i586.pkg \
       -target
      for the non-LDAP macOS Command Line Client.
      sudo -S installer -verbose -pkg /tmp/ipr-cmd-ldap-4.9.m-n.i586.pkg \
       -target
      for the LDAP-enabled macOS Command Line Client.

      Where m and n represent the service update level.

  5. Follow the instructions provided in the installer to finish the installation.
  6. Remove the DVD-ROM.
  7. Create a shell script in the language of your choice or manually set these environment variables:
    PDHOST
    The name of the host where the InfoPrint server is located.
    PD_SOCKET
    The TCP/IP socket number of the port for the InfoPrint server. The default socket is 6874. Use 6874 unless your system has been specifically set up differently, or you have more than one InfoPrint Manager server running on the host.
    PDPRINTER
    The default logical destination in the InfoPrint Manager server. The commands will use this value if you do not specify a logical destination (the -P DestinationName flag) on the command line.

    This example shows a Korn shell script to set the environment variables:

    export PDHOST="hostname-of-infoprint-server"
    export PD_SOCKET="6874"
    export PDPRINTER="name-of-default-logical-destination"
    

  8. Test the system:
    1. Open a command line window.
    2. Set the environment variables as directed in step 7, either manually or using a shell script.
    3. Issue one of the chosen commands, followed by the -h flag to display the syntax of that command and verify the installation.

      For example:

      pdls -h

    4. Arrange for all users of the macOS Command Line Clients to set the environment variables as directed in step 7, whenever they log in. You can use either of these methods:
      • Set the environment variables in the default shell configuration file, either individually or by invoking the shell script.
      • Tell each user to set the environment variables in his or her own shell configuration file, either individually or by invoking the shell script.
Note: To perform a correct installation, use a macOS account with admin rights.