Previous     Contents     Next     
iPlanet Portal Server: Mobile Access Pack Installation Guide



Chapter 2   Installing the Software


You must install Mobile Access Pack on each server where iPlanet Portal Server is installed. This chapter provides instructions for the following installations:

  • Installing iPlanet Portal Server 3.0, Service Pack 3a and Mobile Access Pack at the same time


    Note

    Before you can use the Mobile Access Pack, you must install iPlanet Portal Server 3.0, Service Pack 3a.


  • Installing Mobile Access Pack only, when you already have installed iPlanet Portal Server 3.0, Service Pack 3a

  • iPlanet Messaging Server 5.1, if you have not already installed Messaging Server and you plan to use it to deliver the mail feature to your mobile device user

  • iPlanet Calendar Server 5.0p3, if you have not already installed Calendar Server and you plan to use it to deliver the calendar feature to your mobile device user


    Note

    To achieve optimum performance, install Messenger Server and Calendar Server on a separate machine from Portal Server.


Before you begin installing Mobile Access Pack, read Chapter 1 of this book to ensure that your system requirements are satisfied.



Portal Server and Mobile Access Pack


To install Portal Server and Mobile Access Pack at the same time, complete the following steps:

  1. Insert the Mobile Access Pack CD-ROM, or download the software from this web site:

    http://www.iplanet.com/downloads/download/

    Download all of the iPlanet Portal Server: Mobile Access Pack files and run the script assembleiPSMAP3SP3a, which is one of these files.

  2. To install Portal Server, use the installation instructions in the iPlanet Portal Server 3.0, Service Pack 3a Release Notes document, which is available at this web site:

    http://docs.iplanet.com/

  3. Change to root using the su root command.

  4. Execute the following command:

    ./install

  5. When the Log file located at message appears, record the log file's location.

  6. From another terminal window, execute this command to monitor your installation's progress:

    tail -f logfilename

  7. Read the license agreement when the prompt appears and type yes if you wish to continue with the installation.

  8. If you are installing this software on the same machine as Messaging Server and Calendar Server, provide a unique port number when you respond to the the What is the port for the directory server? prompt.


    Note

    You cannot assign the same port to Portal Server and Messaging Server.

    Messaging Server contains Netscape Directory Server 4.13, and by default this server uses port 389 for Directory Server. This instance of Directory Server is not the same Directory Server that Portal Server uses.




Mobile Access Pack

To install the Mobile Access Pack, when you already have iPlanet Portal Server 3.0, Service Pack 3a installed, complete the following steps:

  1. Change to root using the su root command.

  2. Stop the Portal Server using this command:

    /etc/init.d/ipsserver stopall

  3. Use the cd command to change to the directory where the Web Server is installed and use the ls command to identify how many server instances you have.

    Here is an example of an installation with three server instances:

    # cd /opt/iplanet/server4
    # ls
    README.txt                             bin
    extras                                 setup
    https-1.red-a.iplanet.com
    https-1.red-b.iplanet.com@444
    https-1.red-c.iplanet.com@8080

  4. Use the cd command to change to each Web Server's directory, and use the ./stop command to stop each server.

  5. Use this command to verify that all server processes are stopped:

    ps -ef | grep https

  6. Stop all instances of Web browsers by closing them.

  7. Use this command to verify that the port for each Web Server is free:

    netstat -a | grep "\.port[^ ]"

    Replace port with the value you assigned to iPS port during installation. For example:

    netstat -a | grep "\.8080[^ ]"

    Whenever any output, such as WAIT or CLOSE, is returned, repeat the command.


    Note

    It may take up to a minute before each port is freed.


  8. Insert the Mobile Access Pack CD-ROM, or download the software from this web site:

    http://www.iplanet.com/downloads/download/

    Download all of the iPlanet Portal Server: Mobile Access Pack files and run the script iPSMAP3, which is one of these files.

  9. Execute the following command:

    ./mapinstall

  10. Select the option to install the Mobile Access Pack software.

  11. When the Log file located at message appears, record the log file's location.

  12. From another terminal window, execute this command to monitor your installation's progress:

    tail -f logfilename

  13. Read the license agreement when the prompt appears and type yes if you wish to continue with the installation.

  14. Be prepared to respond to other queries should the installation detect discrepancies with system requirements and similar issues.


    Note

    These queries appear should the Mobile Access Pack installation detect questions about issues such as your user name, iPlanet Portal Sever installation, operating environment, and disk space.


  15. Start the Portal Server using this command:

    /etc/init.d/ipsserver startall



Messaging Server

To use Mobile Access Pack software to provide the iPlanet Messaging Server mail to your mobile device user, you must install and configure iPlanet Messaging Server 5.1. You must complete the steps in this section if you have not already installed Messaging Server.

The Messaging Server software is available for download at this web site:

http://www.iplanet.com/downloads/download/

Installation instructions and other documentation for this product are available at:

http://docs.iplanet.com/

When your Messaging Server installation is completed, use the iPlanet Delegated Administrator to create and enable users for mail services.

To do this, complete the following steps:

  1. Go to this URL:

    messaging_server_name:8080/nda/start.htm

  2. Select log in.

  3. Enter your service administrator Login ID (for example: ServiceAdmin@siroe.iplanet.com) and then enter your password.

  4. In the right pane of the console, expand your domain by selecting your default domain.


    Tip

    Internet is shown as root.

    If your default domain is siroe.iplanet.com, you would select com, then iplanet, and then siroe.


  5. Select the New User icon to display the Create User window.

  6. Create a new user.


    Note

    The First Name, Last Name, Password, Confirm Password and Email address fields are required. The other fields are optional.


  7. From the menu options in left of the Create User window, select Enable Additional Services.

  8. Select Mail.

  9. Select OK to save this user and then select Continue.

  10. When you have created your new users, repeat step 6 through step 9 to create a new user with the following Login ID:

    calmaster


    Note

    A user with this name is required to install Calendar Server. You can omit this step if you do not plan to offer the calendar feature to your mobile device users.


  11. Open a terminal window and enter the following command to synchronize your data with your Messaging Server directory:

    msg_install_directory/msg-host_name/imsimta dirsync -F


    Note

    When your Messaging Server installation is complete, log on as a user and verify that the software is working correctly. Your users must be able to access mail and the address book via Messaging Server.




Calendar Server

To use the Mobile Access Pack software to provide the iPlanet Calendar Server calendar to your mobile device user, you must install and configure iPlanet Calendar Server 5.0p3. You must complete the steps in this section if you have not already installed Calendar Server.

The Calendar Server software is available for download at this web site:

http://www.iplanet.com/downloads/download/

Installation instructions and other documentation for this product are available at:

http://docs.iplanet.com/


Note

When your Calendar Server installation is complete, log on as a user and verify that the software is working correctly. Your users must be able to access the calendar via Calendar Server.




Post-Installation Tasks


This section provides information about post-installation tasks you should complete. The tasks include:

  • Recording information about your installations

  • Reducing the Portal Server session cookie name


Recording Information

Various administration tasks for the Mobile Access Pack require information about your Portal Server, Messaging Server, and Calendar Server installations.

For future reference, you may find it useful to record the following information about your software installations now:

  • Portal Server port number

  • IMAP server name

  • Calendar server name

  • SMTP server name

  • Messenger Express URL

  • Calendar Express HTTP port

  • Address book directory (LDAP) server name

  • Address book directory (LDAP) server port

  • Address book admin DN


    Tip

    To obtain the address book admin DN, perform the following steps:

    1. As root, log in to the iPlanet Messaging Server 5.1 server machine.

    2. Issue a command of the form:

    /usr/iplanet/server5/msg-hostname/configutil | grep local.service.pab.ldapbinddn

    This returns the address book admin DN.


  • Address book admin password


    Tip

    To obtain the address book password, perform the following steps:

    1. As root, log in to the iPlanet Messaging Server 5.1 server machine.

    2. Issue a command of the form:

    /usr/iplanet/server5/msg-hostname/configutil | grep local.service.pab.ldappasswd

    This returns the address book admin password.


  • Address Book directory (LDAP) search base


    Tip

    To obtain the directory search base, perform the following steps:

    1. As root, log in to the iPlanet Messaging Server 5.1 server machine.

    2. Issue a command of the form:

    /usr/iplanet/server5/msg-hostname/configutil | grep local.ugldapbasedn

    This returns the directory search base.


  • Authentication directory (LDAP) server name.

  • Authentication directory (LDAP) server search base.


Shortening the Session Cookie Name

Reduce the length of the Portal Server session cookie name to minimize the length of URLs. This is important when you support mobile devices with small content buffers.

To shorten the name, complete these steps:

  1. Log in as root.

  2. Stop the Portal Server using this command:

    /etc/init.d/ipsserver stopall

  3. Use the cd command to change to the /etc/opt/SUNWips directory.

  4. Edit each platform.conf file to shorten ips.cookie.name=name to something with fewer characters (for example: ips.cookie.name=iPS).

  5. Start the Portal Server using this command:

    /etc/init.d/ipsserver startall


Previous     Contents     Next     
Copyright © 2001 Sun Microsystems, Inc. All rights reserved.

Last Updated November 14, 2001