|
Sun Java Enterprise System 2005Q1 Technical Note |
Sun Java™ Enterprise System Technical Note: Deploying Java Enterprise System on a Single Host for Evaluation
2005Q1
Part Number 819-2201-10
The Sun Java Enterprise System 2005Q1 Technical Note: Deploying Java Enterprise System on a Single Host for Evaluation describes how to install Java™ Enterprise System on one computer for a functioning deployment suited for the evaluation and testing of Sun Java™ System Communications Services 6 2005Q1 and Sun Java™ System Portal Server 6 2005Q1, including Sun Java™ System Portal Server Mobile Access 6 2005Q1.
Caution
This evaluation has been verified in many different environments. However, every deployment is unique, so you may not experience a completely trouble-free installation.
This technical note contain the following sections:
Technical Note Revision History
Scenario OverviewThis section provides an overview of this deployment scenario, the hardware and software used, and the procedures you follow to install, configure, and use this deployment.
This section contains the following topics:
Installation Overview
This scenario results in a functioning deployment suited for the evaluation and testing of Communications Services 6 2005Q1 and Portal Server 6 2005Q1 products. These instructions are not intended to act as a replacement for the individual component documentation, but to merely guide the evaluator through an initial installation.
If you want to include Mobile Access 6 2005Q1 in this evaluation, note that it supports the use of the following software:
- Previous versions of Sun ONE™ Calendar Server and Sun ONE™ Messaging Server (that is, Sun ONE Calendar Server 5.1.1 and Sun ONE Messaging Server 5.2)
- The latest Calendar Server and Messaging Server versions that are part of Java Enterprise System (that is, Sun Java™ System Calendar Server 6 2005Q1 and Sun Java™ System Messaging Server 6 2005Q1)
Note
This example uses Java Enterprise System 6 2005Q1 software. A previously released document, the Sun Java Enterprise System 2003Q4 Deployment Example Series: Evaluation Scenario (http://docs.sun.com/app/docs/doc/817-5419), also shows you how to set up a single machine installation, but it uses Sun Java™ Enterprise System 2003Q4 software. This example also uses the communications channels connected to the new Communications Express client rather than to the older Messenger Express and Calendar Express clients as described in the Sun Java Enterprise System 2003Q4 Deployment Example Series: Evaluation Scenario.
What Components Are Installed?
This example guides you through installing the following Java Enterprise System components:
- Sun Java System Messaging Server 6 2005Q1
- Sun Java System Calendar Server 6 2005Q1
- Sun Java™ System Instant Messaging 7 2005Q1
- Sun Java™ System Directory Server 5 2005Q1
- Sun Java™ System Access Manager 6 2005Q1
- Sun Java™ System Web Server 6 2005Q1
- Sun Java™ System Portal Server 6 2005Q1
- Sun Java System Portal Server Mobile Access 6 2005Q1
The example installation in this document uses the following example data that you change according to your installation:
This example installs all of the software on a single system. Adjust host names accordingly if you install the components on multiple systems.
Recommended Ports
For convenience, this example uses a set of recommended ports. If you use different ports, make sure that your port numbers map to those provided below. For example, this document uses port 390 for the Access Manager admin port. If you decide to use port 3333 for this port, make sure that you change 390 to 3333 everywhere the example references the Access Manager admin port.
Note
Unless otherwise indicated, all of the examples and instructions in this document assume you are logged in as root.
Installation Steps
Installing this example involves the following high-level steps:
- Preparing the system for Java Enterprise System
- Running the Java ES installer and selecting the necessary components
- Installing Messaging Server, Calendar Server, Instant Messaging, Web Server, Directory Server, Access Manager, Portal Server, and Mobile Access
- Patching the system
- Configuring Messaging Server
- Configuring Delegated Administrator
- Configuring Instant Messaging
- Configuring Calendar Server
- Configuring Communications Express
- Configuring Single Sign-on
- Configuring a Portal User
System Requirements
This section describes the hardware and software requirements for this example.
Table 3 Client Software Requirements
Component
Platform Requirement
Browser
Netscape 7.x or later, or IE 5.x or later
Installation Time Estimates
The following table provides time estimates for installing this example.
Table 4 Installation Time Estimates
Phase
Number of Hours
Solaris 9 OS with Language Support
2
Software installation
2
Software configuration
3
Total
7 hours (average)
As part of the configuration, you will need to add data to Messaging Server and Calendar Server.
Installation Notes and Recommendations
- With Solaris 9, ftp might not work for certain accounts.
These accounts are listed in /etc/ftpd/ftpusers. Just remove the account from this list (for example, root) and you will be able to ftp as that user.
- Use gzip -d or gunzip to decompress the *gz files.
- Choose a “good” password (minimum eight characters) and use it throughout the installation, unless, of course, you are very good at remembering different passwords for different products.
Expected User Input
During installation, your are prompted for various input. User input is indicated by text of the form <user-input>. Table 5 helps you plan for the types of information you must provide during installation.
Configuration Information Used in the Example
The example installation is performed on a single system with the following network identity:
The following table lists the installation options, directories, and port numbers used to configure the servers in the example installation.
Installing the ExampleThis section describes how to install the components on a single machine for evaluation purposes. The other components are configured after installation, using component configuration tools.
This section contains the following topics:
Checking Installation Requirements
Before you install components, use the steps in this section to make sure the computer on which you are installing is ready.
To Check System Requirements
The computer should meet the following requirements:
To Check DNS
Verify that DNS is running and configured properly:
- Make sure that the /etc/resolv.conf file has name server entries with the IP addresses of valid name servers. For example:
nameserver 192.168.100.22
nameserver 192.168.100.23
nameserver 192.168.100.24
nameserver 192.168.100.25
- Make sure that the /etc/hosts file has an entry for the fully qualified host name of the server. This fully qualified host name should be listed before the non fully qualified host name. For example:
- Make sure that the /etc/nsswitch.conf file is configured to use files first to resolve host names. The hosts line in the nsswitch.conf file should list files first in its entry:
To Unzip the Java Enterprise System Zip File
Installing the Components
You install Java Enterprise System components by running the Java Enterprise System installer.
To Start the Installer
- Log in as root to the machine on which you are installing Java Enterprise System.
- Change to the /tmp/JES3 directory where you stored and unzipped the Java ES zip file.
- Change to the Solaris_sparc platform directory.
- Start the Java Enterprise System installer in graphical mode.
./installer &
- Accept the license and select language(s). English is installed by default.
- Select the following products.
- Sun Java System Messaging Server 6 2005Q1
- Sun Java System Calendar Server 6 2005Q1
- Sun Java System Instant Messaging 7 2005Q1
- Sun Java System Portal Server 6 2005Q1 (includes Mobile Access)
- Sun Java System Communications Express 6 2005Q1
- Sun Java System Web Server 6.1 SP4 2005Q1
- Sun Java System Access Manager 6 2005Q1 and all supporting software
- Sun Java System Directory Server 5 2005Q1
- Sun Java System Administration Server 5 2005Q1
- Click Next to continue.
- Click Next to upgrade shared components.
Locations:
- Directory Server root: /opt/DSServers (changed from /var/opt/mps/serverroot)
- Directory Preparation Tool: /opt/SUNWcomds
- Access Manager: /opt (will create /opt/SUNWam)
- Web Server: /opt/SUNWwbsvr
- Instant Messaging: /opt (will create /opt/SUNWiim)
- Calendar Server: /opt (will create /opt/SUNWics5)
- Messaging Server: /opt/SUNWmsgsr
- Communications Express: /opt/SUNWuwc
- Portal Server: /opt (will create /opt/SUNWps)
- The system performs a check. When done, click Next.
If you are installing on Solaris 9, you might need to install the following patches: 112785-35, 113096-03. Install 113096-03 first. After installing all patches using the patchadd command, reboot the system.
- Choose Configure Now then click Next.
- The following components must be configured after installation:
- Click Next to configure the remaining components.
To Select Common and Web Server Settings
This installation assumes the use of Sun Java System Web Server. You may choose an alternate web container but that is beyond the scope of this document.
- The installation script prompts for a series of options. The following table shows how to respond to the Common and Web Server configuration options.
To Select Directory Server Settings
- The following table shows how to respond to the Directory Server configuration options.
To Select Administration Server Settings
- The following table shows how to respond to the Administration Server configuration options.
To Select Access Manager Settings
- The following table shows how to respond to the Access Manager configuration options.
To Select Portal Server Settings
- The following table shows how to respond to the Portal Server configuration options.
To Complete the Installation
- Click Next when you are satisfied with the Ready to Install list.
The shared components are upgraded. This takes some time.
- When the installer finishes upgrading shared components, it displays the Product Registration page. Deselect Open Registration Window.
- Click Install to install the Java Enterprise System components.
- When installation is complete, the Installation Complete page is displayed. Click Close to exit the installer.
To Verify the Installation
Once the installation has completed, start LDAP and Portal Server and verify that they work.
- Change to the /opt/DSServers directory.
- Change to the slapd-wireless directory.
- Start LDAP:
./start-slapd
- Change to the /etc/init.d directory.
- Start Access Manager:
./amserver start
- Change to the /opt/SUNWwbsvr/https-wireless.map.beta.com directory.
- Start Web Server:
./start
- Verify that you can log in to the Access Manager console as amadmin. The URL for the Access Manager console is:
http://fully-qualified-hostname:portal-server-port/amconsole
In this example, type:
http://wireless.map.beta.com/amconsole
Use amadmin and adminpass as the user ID and password.
- Proceed to Configuring Components for instructions on how to configure Java Enterprise System.
Uninstalling the Components
After you complete your evaluation, you can use the Java Enterprise System uninstaller to remove the components that you installed. See Chapter 12, “Uninstalling Components,” in the Sun Java Enterprise System 2005Q1 Installation Guide:
Patching the ExampleAfter completing the installation portion of this example deployment, you need to apply the following patches before configuring components:
To Install Patches
- Obtain patches from the Sunsolve site: http://sunsolve.sun.com
- Click Patch Portal.
- Type the patch number in the PatchFinder text box, and click Find Patch.
For example, enter patch number 117784 to find the latest release of this patch, rather than 117784-10, which will only find that specific release of the patch.
- Download the zip file for the patch.
- Expand the zip file.
For example:
unzip 117784-10.zip
A directory is created for the patch files.
- Apply the patch.
For example:
patchadd 117784-10
As patches are updated over time, the patches you download will likely be of a different revision than those used in this example. Be sure to use the most current version of the patches.
Configuring ComponentsThis section describes how to configure and start the components that you use in this evaluation deployment.
This section contains the following topics:
Before You Begin
Before you configure the Messaging Server software, you need to create the mailsrv user and disable the sendmail process.
To Create the mailsrv User
- Messaging Server requires a mail server user, which must exist before you can finish the installation. You can skip this step, because the group and user are created during the configuration time. However, you might want to create the mailsrv user yourself as shown below. For this installation, use the useradd command to create a user with username mailsrv and group mail. You use this ID in Step d (under Step 7).
Type the following commands to create the user mailsrv with a group ID of mail, and a user home directory of /export/home/mailsrv. (This assumes the /export/home directory already exists.)
To Disable sendmail
Preparing the Directory and Configuring Messaging Server
This section explains how to prepare the Directory Server LDAP schema and configure Messaging Server.
To Apply Schema 2 to Your Directory Tree
- Change to the /opt/SUNWcomds/sbin directory, where the comm_dssetup script is located.
- Run the comm_dssetup.pl script:
/opt/DSServers/bin/slapd/admin/bin/perl comm_dssetup.pl
The perl script prompts for a series of options. The following table shows how to respond to the prompts.
- Confirm your choices. The comm_dssetup script proceeds.
- When prompted, choose to continue with script.
Continue with the next step after the comm_dssetup script finishes and displays its “successful completion” message.
- Change to the /opt/SUNWmsgsr/sbin directory, where the Messaging Server configure script is located.
- Run the Messaging Server configure script:
./configure
The Configuration Wizard appears. Read the introductory information and proceed by clicking Next.
- Verify the following:
- Fully qualified host name of Messaging Server, FQHN: [wireless.map.beta.com]
- Directory to store config/data files: [/var/opt/SUNWmsgsr]
- Install MTA, MS store, and Messenger Express. There is no need to install the Multiplexor for this deployment.
- Name of the mail server Unix user: Unix username [mailsrv]
- Unix group: [mail]
- The installation script prompts for a series of options. Use the following table to respond to the configuration options:
- Click Next, then click Configure Now.
You receive an error about the Webmail port being in use. Click Next to continue. The following step corrects this problem.
- When the configuration is finished, click Next to continue, then click Close to exit.
- Configure the Webmail port:
/opt/SUNWmsgsr/sbin/configutil -o service.http.port -v 2080
- Start Messaging Server:
/opt/SUNWmsgsr/sbin/stop-msg
/opt/SUNWmsgsr/sbin/start-msg
Configuring Delegated Administrator and Communications CLI
This section describes configuring Delegated Administrator console and utility, which are used for user management.
To Configure Delegated Administrator
- Change to the directory where the configuration script was installed:
cd /opt/SUNWcomm/sbin
- Run the configurator script:
./config-commda
- Accept the default for the Directory to store User Mgmt data files: [/var/opt/SUNWcomm]
- Install Delegated Administrator Utility, Console, and Server.
The installation script prompts for a series of options. Use the following table to respond to the configuration options:
- Select Configure Now.
- Click Next to continue.
Two warnings appear: one is remind you to restart Web Server; the other is to remind you to enable the mail and calendar domains. The next steps correct these problems.
- When the configuration is finished, click Close to exit.
- Restart Web Server:
cd /opt/SUNWwbsvr/https-wireless.map.beta.com
./stop
./start
- Modify the mail and calendar domains, and create users by using the commadmin utility:
Create as many users as you need. The Instant Messaging configuration steps in the next section show how to add Presence and Instant Messaging services to those users.
Configuring Instant Messaging
Configuring Instant Messaging is important for the completeness of the demo but is not necessary for Mobile Access.
- Change to the directory where the Instant Messaging configuration script is located:
cd /opt/SUNWiim
- Run the Instant Messaging configurator script:
./configure
- Install all services and verify the following:
- Check both Access Manager (Identity Server) options for SSO and Policy.
- Verify locations and ports:
- Verify LDAP configuration:
- Set the SMTP Server to wireless.map.beta.com.
- Set codebase to http://wireless.map.beta.com:80/im.
- Assign Instant Messaging to existing users.
- Start Instant Messaging after successful configuration and on system startup.
After clicking Next, wait a few minutes for Instant Messaging to be configured.
- At the Configuration Summary screen, click Close to exit.
- Create a link to Instant Messaging in the /opt/SUNWwbsvr/docs directory:
cd /opt/SUNWwbsvr/docs
ln -s /opt/SUNWiim/html im
- Edit the Instant Messaging portlet in the Portal Server Desktop to include the proper ports and parameters.
Note
You might have to execute these steps after you have added the mail and calendar services to Access Manager, because you might not be able to access the Portal Desktop until that service has been registered.
- In your web browser, open a URL for the Access Manager console and log in as amadmin (password is adminpass.) The URL for the Access Manager console is:
http://fully-qualified-hostname:portal-server-port/amconsole
In this example, type:
http://wireless.map.beta.com/amconsole
- Choose Services from the View menu in the left pane.
- Click the properties icon for Portal Desktop Service.
The properties appear in the right pane.
- Click the Manage Channels and Containers link in the right pane.
- Scroll to the bottom of the right pane where the Channels are listed. You will see a channel labeled IMChannel. Click the Edit Properties link to the right of the channel name and type the following attributes:
- When done, click Save.
Configuring Calendar Server
This section shows you how to run the Calendar Server configuration script.
- Change to the directory where the configuration script is located:
cd /opt/SUNWics5/cal/sbin
- Run the Calendar Server configurator script:
./csconfigurator.sh
- Verify the correct Administration and LDAP information.
- LDAP Server Host Name: wireless.map.beta.com
- LDAP Server Port: 389
- Verify the Directory Manager DN as cn=Directory Manager. Type the password as adminpass.
- The Base DN should be o=map.beta.com,o=isp (you might need to edit this value.)
- Administrator User ID: calmaster
- Type the Administrator password as adminpass.
- After verifying and typing or modifying the required information, click Next to continue.
- Verify Email information:
- After verifying and entering or modifying the required information, click Next to continue.
- Verify the correct Runtime configuration:
- The Service Port should be set to 3080.
- Maximum sessions and threads can be left at default values, 5000 and 20 respectively.
- The Number of Server processes can be left at the default value, which is generally the number of CPUs in a system.
- Accept the default Runtime User ID and Runtime Group ID. The default User ID is icsuser and the default Group ID is icsgroup. If this group does not exist, you will be prompted to create the group and the user later.
- Enable automatic starting of Calendar server on reboot only, not after configuration. (Deselect “Start after successful configuration.”)
- After verifying and typing or modifying the required information, click Next to continue.
- Verify the locations to store configuration and data files:
- After verifying the required information, click Next to continue.
- You are prompted to create the new directories if they do not exist. Create them.
- Enable Archive and Hot Backup. Accept the defaults:
- Accept default Archive directory: /var/opt/SUNWics5/csdb/archive
- Accept default Hot Backup directory: /var/opt/SUNWics5/csdb/hotbackup
- Accept default Minimum & Maximum archive lengths: 3 days and 6 days respectively
- Accept default Minimum & Maximum hot backup lengths: 3 days and 6 days respectively
- Hot backup checkbox should be checked “Same as archive”
- You are prompted to create the new directories if they do not exist. Create them.
- Click the Configure Now button to configure Calendar Server.
The Configuration begins. Configuration takes less than one minute. Click the Details button to verify that all packages configured correctly. Click the Close button to exit the configurator.
- Start the Calendar Server daemons:
cd /opt/SUNWics5/cal/sbin
./stop-cal
./start-cal
- To log in to Calendar Server, open a browser and type the name of the system in the URL. In this example, type:
http://wireless.map.beta.com:3080
You are prompted for a user name and password. If you created a user according to the previous steps in this section, type jdoe for the user name, and demo for the password.
- Verify that you can log in with one of the users you previously created by using the Access Manager console.
Configuring Communications Express
This section shows you how to run the Communications Express configuration script.
- Change to the directory where the configuration script is located:
cd /opt/SUNWuwc/sbin
- Run the Communications Express configurator script:
./config-uwc
- Accept the default for Directory to store configuration and data files: [/var/opt/SUNWuwc]
- Install the Mail and Calendar Components.
The installation script prompts for a series of options. Use Table 15 to respond to the configuration options:
Table 15 Values for config-uwc Script
Option
[Default Value]
Enter:
Hostname
[wireless]
accept default
DNS Domain
[map.beta.com]
accept default
Web Container
[Web Server]
accept default
Web Server root Directory
[/opt/SUNWwbsvr]
accept default
Web Server Instance Identifier
[wireless.map.beta.com]
accept default
Virtual Server Identifier
[https-wireless.map.beta.com]
accept default
HTTP Port
[80]
accept default
Web Container User ID
[webservd]
root
Web Container Group IP
[webservd]
other
URI Path
[/uwc]
accept default
Hosted Domain Support
[No]
accept default
URL of Directory Server
[ldap://wireless.map.beta.com:389/]
accept default
Bind DN
[cn=Directory Manager]
accept default
Password
--
adminpass
DC Tree suffix
[o=isp]
accept default
Default Domain
[map.beta.com]
accept default
IS Login URL
[http://wireless.map.beta.com:80/amserver/UI/Login]
accept default
IS Administrator DN
--
uid=amadmin,ou=people,o=isp
IS Administrator Password
--
adminpass
Messenger Express Port
[80]
2080
Calendar Server Hostname
[wireless.map.beta.com]
accept default
Calendar Server Port
[9004]
3080
Calendar Admin user ID
[calmaster]
accept default
Calendar Administrator User Password
--
adminpass
URL of PAB Directory Server
[ldap://wireless.map.beta.com:389]
accept default
Bind As
[cn=Directory Manager]
accept default
Password
--
adminpass
- Click the Configure Now button to configure Communications Express.
- After the configuration is finished, click Next, then click Close.
- Restart Web Server:
cd /opt/SUNWwbsvr/https-wireless.map.beta.com
./stop
./start
Configuring Single Sign-on (SSO) for Communications Products
To set up SSO for Communications Express and for Access Manager/Portal Server, you edit the uwcauth.properties file in the /var/opt/SUNWuwc/WEB-INF/config/ directory. You also need to run the configutil utility for Messaging Server properties, and edit the ics.conf file for Calendar Server.
To Configure Communications Express for SSO
- Verify the following settings in the /var/opt/SUNWuwc/WEB-INF/config/uwcauth.properties file:
uwcauth.identity.enabled=true
uwcauth.identity.login.url=http://wireless.map.beta.com:80/amserver/UI/Login
uwcauth.identity.binddn=uid=amadmin,ou=people,o=isp
uwcauth.identity.bindcred=adminpass
uwcauth.identity.cookiename=iPlanetDirectoryPro
uwcauth.http.port=80
uwcauth.https.port=443
- Restart Web Server if you change any of the above settings.
To Configure Messaging Server for SSO
- To enable Communications Express users to access Messenger Express using the Access Manager session, run the following configutil commands:
# cd /opt/SUNWmsgsr/sbin
# ./configutil -o local.webmail.sso.amnamingurl -v http://wireless.map.beta.com:80/amserver/namingservice
# ./configutil -o local.webmail.sso.uwcenabled -v 1
# ./configutil -o local.webmail.sso.uwclogouturl -v http://wireless.map.beta.com:80/uwc/base/UWCMain\?op=logout
# ./configutil -o local.webmail.sso.uwcport -v 80
# ./configutil -o local.webmail.sso.uwccontexturi -v "uwc"
# ./configutil -o local.webmail.sso.amcookiename -v iPlanetDirectoryPro
# ./configutil -o local.webmail.sso.uwchome -v http://wireless.map.beta.com/uwc
# ./configutil -o service.http.allowadminproxy -v yes
# ./configutil -o service.http.ipsecurity -v no
# ./stop-msg
# ./start-msg
To Configure Calendar Server for SSO
- Stop Calendar Server:
cd /opt/SUNWics5/cal/sbin
./stop-cal
- Edit the /opt/SUNWics5/cal/config/ics.conf file (in a text editor such as vi) and make the following changes:
service.http.allowadminproxy = "yes"
local.calendar.sso.amnamingurl = "http://wireless.map.beta.com:80/amserver/namingservice"
local.calendar.sso.singlesignoff = "yes"
local.calendar.sso.amcookiename = "iPlanetDirectoryPro"
local.calendar.sso.logname = "am_sso.log"
service.calendarsearch.ldap = "no"
service.http.ipsecurity = "no"
To Configure Instant Messaging Calendar Notifications
- Edit the /opt/SUNWics5/cal/config/ics.conf file (in a text editor such as vi) and make the following changes:
caldb.serveralarms = "1"
caldb.serveralarms.dispatch = "yes"
caldb.serveralarms.url = "enp:///ics/customalarm"
caldb.serveralarms.contenttype = "text/calendar"
caldb.serveralarms.dispatchtype = "ens"
- Restart Calendar Server:
cd /opt/SUNWics5/cal/sbin
./start-cal
Verifying Single Sign-on (SSO) Configuration
This section describes how to verify the SSO configuration for Communications Express client, Delegated Administrator, and Instant Messenger. You simply verify that you can log in to the various services. After you are satisfied that you can log in, log out.
- In your web browser, open the following URL for the Communications Express client:
http://wireless.map.beta.com/uwc
- Log in as one of the users created earlier.
If you created a user according to the previous steps, type jdoe for the user name, and demo for the password.
- In your web browser, open the following URL for Delegated Administrator:
http://wireless.map.beta.com/da/DA/Login
- Log in as user admin.
The password is adminpass.
- In your web browser, open the following URL for Instant Messenger:
http://wireless.map.beta.com/im/en/im.jnlp
Note
If you cannot log into Instant Messaging as a user, you might need to manually add the Instant Messaging and Presence Services to the user. See To Add Services to the Lower Level Organization for more information.
Configuring Portal Server
The following procedures enable Portal Server services to permit a portal user to gain access to Communications Channel and Mobile Access functionality.
To Log In to Access Manager
To Add Services to the Lower Level Organization
If you set your Organization DN to o=map.beta.com,o=isp, you need to add Portal Server services to the map.beta.com organization. Once these services have been added to the suborganization, you add the necessary services to each user in this suborganization.
Note
Previously, you created a set of users with the commcli command. These users exist in the map.beta.com organization. At this point, there are no Services defined for these users. You need to register the services with these users for them to be able to log in to Portal Server.
- Upon logging into the Access Manager console, you are presented with a view of all your organizations. The map.beta.com organization is listed. Click the link to map.beta.com.
- Choose Services from the View menu in the left pane.
- Click the Add button.
- Either click the individual services to add to this organization, or click on the box at the top of the list that shows two checkboxes. This selects all the services. Upon selecting all the services, click the OK button to add all the services to the suborganization.
- Within this same suborganization, click the properties icon next to the name of all the services.
You see that a template does not exist for these services. You might want to create a template.
Note
Creating new templates in suborganizations is useful if the values in the suborganization will be different from those in the top level organization. When you create a new template, values for the attributes might automatically change to default values, not the values that you thought were assigned. Hence, it is best not to create a separate template unless absolutely necessary.
One of the values that changes is Portal Desktop Type in the Portal Desktop service. You need to change the value from default to sampleportal.
If you do not create service templates, then the service parameters are inherited from the higher level organization.
- Click the Yes button when prompted to create a template.
It is not necessary to create a template. If one does not exist, the properties of the service will be inherited from the top level organization.
- Choose Users from the View menu.
A list of users is presented. You need to add the services you just registered in this suborganization to each user.
- Click the property icon beside a user.
- In the right pane, open the View drop-down menu and choose Services.
No services are listed.
- Click the Add button.
A list of services appears.
- Click the double-checked box at the top of the list of services to add all services. Then click the OK button.
Configuring Address Book SSO Adapter Template
Note
This section is applicable only to the Messenger Express personal address book Portal Server channel. Skip this section if you are using the Communications Express Address Book Channel.
The following steps enable use of the Personal Address Book (PAB). Perform these steps very carefully to help insure the correct operation of address book related features.
To Configure the Address Book SSO Adapter Template
- From the previous section, you should still be logged in to the Access Manager console.
- Click the Service Configuration tab.
- In the left pane, click the property arrow for SSO Adapter.
The SSO Adapter Templates list appears in the right hand panel. There should be an entry labeled [SUN-ONE-ADDRESS-BOOK].
- Click the New button to create a template without brackets in the name.
Type in the name SUN-ONE-ADDRESS-BOOK.
- Choose the Existing Template [SUN-ONE-ADDRESS-BOOK].
- Click the Create button.
A list of editable properties should appear with their corresponding values.
- The SSOAdapter Template takes the form of a very long URL. Within the default value of this URL, several values appear for which substitutions must be provided. These values are indicated as hyphen-separated, all uppercase names, contained within square brackets. Edit the values appearing in the editable text boxes, and perform the following substitutions:
- [SERVER-NAME:PORT]: Specifies the name of the LDAP server providing the PAB service, that is, wireless.map.beta.com:389.
- [PAB-SEARCH-BASE]: Specifies the LDAP search base of the PAB. Assuming that a default Messaging Server installation was done, a value of o=pab should suffice.
- [USER-SEARCH-BASE]: Specifies the LDAP search base for users. Using our Messaging Server installation example, a value of o=map.beta.com,o=isp should suffice.
- [ADMIN-ID]: Specifies the DN of the PAB admin. This can be determined by logging in to the back-end machine as root and performing the following steps:
For example: uid=msg-admin-wireless.map.beta.com-20030729221841, ou=People, o=sun, o=isp
- [ADMIN-PASSWORD]: Specifies the password for the PAB admin. This can be determined by logging into the back-end machine as root and performing the following steps:
For example: 7]GV89[1}f
- [IMAP-HOST]: Should specify the name of the IMAP server that is used for authenticating PAB users. Typically, this is the same server name value used when defining [SERVER-NAME:PORT], that is, wireless.map.beta.com.
- [IMAP-PORT]: Should specify the port of the IMAP server that is used for authenticating PAB users. Typically, this is set to 143.
- [CLIENT-PORT]: Should specify the port that provides web application service for PAB. This is typically the port on which Messenger Express service is available. Our example uses client port 2080.
- After making all the substitutions to the SSOAdapter Template string, click the Save button beneath the SSO Adapter Templates list.
- Click Finished.
You should see the new SSOAdapter Template appear in the list.
- Select the check box beside the original template and click Remove.
Note
Removing the original template is optional. As long as the original configName is enclosed in brackets, it does not need to be removed.
- Go to the top of the SSO Adapter panel and click Save.
Configuring Portal and Back-end Servers for Proxy Authentication
You can enable administrator proxy authentication for the Address Book, Calendar, and Mail channels. By enabling administrator proxy authentication, users do not need to edit a channel’s properties (through the channel’s edit page) to input their authentication credentials. Instead, an administrator’s credentials are used and are stored in the SSO Adapter template. To configure administrator proxy authentication, you must perform the following steps. If you do this, you can then skip Configuring a Portal Server User.
To Configure the Portal Mail Channel for the SSO Adapter Service
- At the top level organization where you modified the SSO Template for Address Book, find the Global SSO IMAP Adapter for SUN-ONE-MAIL.
- Click the Edit Properties link.
Move the following attributes from the Merge column to the Default column. You do this by clicking the Change Type button and then moving the attributes from Merge to Default.
- When done moving the attributes, click the Save button.
- Insert values for these default variables.
The keyword merge essentially means that the attribute value is derived from user input. The keyword default means the attribute values are provided in the SSO template. Provide these values:
- enableProxyAuth
The default value is false. Change to true.
- proxyAdminUid
Specifies the name of the Messaging Server admin user. The default value is [PROXY-ADMIN-UID]. In this example, the value is admin.
- proxyAdminPassword
Specifies the password of the admin user. The default value is [PROXY-ADMIN_PASSWORD]. In this example, the value is adminpass.
- host
The value takes the form of fully qualified host. Thus, in this example, the value is wireless.map.beta.com.
- port
This is the value of the IMAP port. In this example, the value is 143.
- smtpServer
This is the value of the SMTP server, which for this example is the same name as the mail host, wireless.map.beta.com.
- clientPort
This is the value of the Messaging Client port, which in this example is 2080.
- smtpPort
This is the value of the SMTP port. In this example, the value is 25.
- Leave the domain field empty.
- serverSSOEnabled
Setting this variable enables the link to launch the application from the channel. The default value is false. Change to true.
- Click Save to save the configuration.
To Configure the Communications Express Mail Channel for SSO Template Configuration
- At the top level organization where you modified the SSO Template for Address Book, find the Global SSO IMAP Adapter for SUN-UWC-MAIL.
- Click the Edit Properties link.
Move the following attributes from the Merge column to the Default column. You do this by clicking the Change Type button and then moving the attributes from Merge to Default.
- When done moving the attributes, click the Save button.
- Insert values for these default variables.
The keyword merge essentially means that the attribute value is derived from user input. The keyword default means the attribute values are provided in the SSO template. Provide these values:
- enableProxyAuth
The default value is false. Change to true.
- proxyAdminUid
Specifies the name of the Messaging Server admin user. The default value is [PROXY-ADMIN-UID]. In this example, the value is admin.
- proxyAdminPassword
Specifies the password of the admin user. The default value is [PROXY-ADMIN_PASSWORD]. In this example, the value is adminpass.
- host
The value takes the form of fully qualified host. Thus, in this example, the value is wireless.map.beta.com.
- port
This is the value of the IMAP port. In this example, the value is 143.
- smtpServer
This is the value of the SMTP server, which for this example is the same name as the mail host, wireless.map.beta.com.
- clientPort
This is the value of the Messaging Client port, which in this example is 2080.
- smtpPort
This is the value of the SMTP port. In this example, the value is 25.
- Leave the domain field empty.
- serverSSOEnabled
Should be true. Setting this variable enables the link to launch the application from the channel.
- Click Save to save the configuration.
To Configure the Calendar Channel for SSO Template Configuration
- At the top level organization where you modified the SSO Template for Address Book, find the Global SSO http Adapter for SUN-ONE-CALENDAR.
- Click the Edit Properties link.
Move the following attributes from the Merge column to the Default column. You do this by clicking the Change Type button and then moving the attributes from Merge to Default.
- When done moving the attributes, click the Save button.
- Insert values for these default variables.
The keyword merge essentially means that the attribute value is derived from user input. The keyword default means the attribute values are provided in the SSO template. Provide these values:
- enableProxyAuth
The default value is false. Change to true.
- proxyAdminUid
Specifies the name of the Calendar Server admin user. The default value is [PROXY-ADMIN-UID]. In this example, the value is calmaster.
- proxyAdminPassword
Specifies the password of the calmaster user. The default value is [PROXY-ADMIN_PASSWORD]. In this example, the value is adminpass.
- host
The value takes the form of fully qualified host. Thus, in this example, the value is wireless.map.beta.com.
- port
You could use a different port number, but in this example the port is 3080.
- clientPort
This is the value of the Calendar Client port, which in this example is 3080.
- serverSSOEnabled
The default value is false. Do not change this value. Setting this variable enables the link to launch the application from the channel.
- Click Save to save the configuration.
To Configure the Communications Express Calendar Channel for SSO Template Configuration
- At the top level organization where you modified the SSO Template for Address Book, find the Global SSO http Adapter for SUN-UWC-CALENDAR.
- Click the Edit Properties link.
Move the following attributes from the Merge column to the Default column. You do this by clicking the Change Type button and then moving the attributes from Merge to Default.
- When done moving the attributes, click the Save button.
- Insert values for these default variables.
The keyword merge essentially means that the attribute value is derived from user input. The keyword default means the attribute values are provided in the SSO template. Provide these values:
- enableProxyAuth
The default value is false. Change to true.
- proxyAdminUid
Specifies the name of the Calendar Server admin user. The default value is [PROXY-ADMIN-UID]. In this example, the value is calmaster.
- proxyAdminPassword
Specifies the password of the calmaster user. The default value is [PROXY-ADMIN_PASSWORD]. In this example, the value is adminpass.
- serverSSOEnabled
The default is true. Do not change this value. Setting this variable enables the link to launch the application from the channel.
- host
The value takes the form of fully qualified host. Thus, in this example, the value is wireless.map.beta.com.
- port
You could use a different port number, but in this example the port is 3080.
- clientHost
Use wireless.map.beta.com as the value.
clientPort
Use 80 as the value.
- Click Save to save the configuration.
To Configure the Address Book Channel for SSO Template Configuration
- Select the Global SSO LDAP adapter for SUN-ONE-ADDRESS-BOOK and make the following substitutions:
- enableProxyAuth
The default value is false. Change to true.
- proxyAdminUid
Specifies the name of the Messaging Server admin user. The default value is [PROXY-ADMIN-UID]. In this example, the value is admin.
- proxyAdminPassword
Specifies the password of the admin user. The default value is [PROXY-ADMIN_PASSWORD]. In this example, the value is adminpass.
- serverSSOEnabled
The default value is false. Change to true. Setting this variable enables the link to launch the application from the channel.
- Click Save to save the configuration.
To Set up Admin Proxy Auth for Messaging Server and Calendar Server
You need to enable the capability to allow proxy authentication on Messaging Server and Calendar Server. These steps should have already been performed in the previous sections, but you verify that they have been set.
Configuring New Communications Express Channels in the Portal Desktop
By default, the communications channels that are displayed in the Portal Desktop are the “old” channels. If you want to display the “new” Communications Express channels in the Portal Desktop, you need to add them to the Desktop container.
Note
The Mobile Access channels should use the “old” channels, since the Communications Express channels are not currently supported by Mobile Access
To Obtain Necessary Portal Server Patch
To enable the Communications Express AddressBook channel, you need to first download and install patch 118950 for Portal Server. This patch corrects problems with the AddressBook channel failing and with proxy authentication.
- Obtain the patch from the Sunsolve site: http://sunsolve.sun.com
- Click PatchFinder.
- Type the patch ID 118950 in the PatchFinder text box, and click Find Patch.
- Download the zip file for the patch.
- Expand the zip file.
For example:
unzip 118950-12.zip
A directory is created for the patch files.
- Apply the patch.
For example:
patchadd 118950-12
To Configure New Communications Express Channels
- In your web browser, open a URL for the Access Manager console and log in as amadmin. The URL for the Access Manager console is:
http://fully-qualified-hostname:portal-server-port/amconsole
In this example, type:
http://wireless.map.beta.com/amconsole
- Log in as amadmin.
The password is adminpass.
- Click the Identity Management tab.
- Go to the top level organization, or, if you created service templates, navigate to the lower level organization.
- Choose Services from the View menu in the left pane.
- Click the property arrow for Portal Desktop.
- In the right pane, the Portal Desktop settings appear. Click the Manage Channels and Containers link.
- Click the MyFrontPageTabPanelContainer link.
- Scroll down until the Ready For Use list appears.
- Select the UWCMail, UWCCalendar, and UWCAddressbook channels.
- Click the Add button to move them to the Available box. Select them again and click the Add button to move them to the Visible on the Portal Desktop box.
- Select AddressBook, Calendar, and Mail (the “old” channels) and move them from the Visible box back up to the Ready For Use box.
This effectively removes them from the Desktop.
- Click Save (under Channel Management).
Configuring UsersThis section describes how to use the Access Manager console to add services to user accounts, the Delegated Administrator utility to create additional users, as well as additional Portal Server configuration steps.
This section contains the following topics:
Configuring User Services
The following steps are required to add mobile services to each of the users that you previously created. If you create additional users, you need to perform these steps as well. The steps enable users to modify their mobile mail or addressbook preferences.
To Add Services to User Accounts
- In a web browser, open the URL for the Access Manager console and log in as amadmin. The URL for the Access Manager console is:
http://fully-qualified-hostname:portal-server-port/amconsole
In this example, type:
http://wireless.map.beta.com/amconsole
- Click the Identity Management tab.
- You will be presented with a view of all your organizations including map.beta.com. Click the map.beta.com link.
- Choose Users from the View menu.
- For each user created, click the property icon to the right of the user’s name.
- In the right pane, Choose Services from the View menu.
- Click the Add button to add new services.
- Select Mobile Address Book, Mobile Calendar, and Mobile Mail checkboxes, as well as any other available services, then click the OK button.
Tip
A shortcut is to click the double-checked box at the top of the list of services to add all services.
- Repeat these steps for other users as needed.
Creating Additional User Accounts and Groups
This section describes how to create additional users accounts and groups. Users and groups created in this fashion work with both Communications Services products and Portal Server.
To Create End User Accounts and Groups
- The following example shows how to create users using the Delegated Administrator command-line utility and also how to create a group consisting of the users created.
# /opt/SUNWcomm/bin/commadmin user create -D admin -F Demo -l demo1 -L One -n map.beta.com -p 80 -w adminpass -W demo -X wireless.map.beta.com -S mail,cal -E demo1@map.beta.com -H wireless.map.beta.com -k legacy
# /opt/SUNWcomm/bin/commadmin user create -D admin -F Demo -l demo2 -L One -n map.beta.com -p 80 -w adminpass -W demo -X wireless.map.beta.com -S mail,cal -E demo2@map.beta.com -H wireless.map.beta.com -k legacy
# /opt/SUNWcomm/bin/commadmin group create -D admin -G Demostaff -n map.beta.com -p 80 -w adminpass -X wireless.map.beta.com -S mail -E Demostaff@map.beta.com -H wireless.map.beta.com -o calmaster -m demo1 -m demo2
- If you are using suborganizations, you need to configure the users for Portal services. See To Add Services to the Lower Level Organization for more information.
To Create User Accounts by Using Delegated Administrator Console
An alternative to using the Delegated Administrator command-line utility to create users is to use the Delegated Administrator console. The high-level steps to create users with Delegated Administrator console are the following:
However, the first time you use Delegated Administrator console, you must add service packs to the organization that contains your users.
To add a user account with Delegated Administrator console:
- In a web browser, open the URL for the Delegated Administrator console and log in as amadmin (password is adminpass):
http://wireless.map.beta.com/da/DA/Login
- Click the check box next to the map.beta.com organization, then click the Allocate Service Package button.
- Select the desired service packages.
Choose from among bronze, silver, and topaz because they have IMAP service enabled. Each service package has a different mail quota.
- Click Next to continue.
- Now select the quantity of each service pack desired.
A quantity of 100 is adequate for demo purposes.
- Click Finish.
- Once the service packs have been allocated for the domain, you can now add users to the domain. Click the domain link, map.beta.com.
- Click the New button to create a new user account within this domain.
- Type a First Name (such as Demo), Last Name (such as Five), Display Name (such as Demo Five), then click Next.
- There is no need to type postal information, so click Next.
- Select a service pack for this user, for example, gold, then click Next.
- Type the email address, for example, demo5@map.beta.com. Mail Delivery Option should be Local Inbox. Mail Service Status should be Active.
- Click Next.
- Type Login ID and Password. In this example, Login ID is demo5 and password is demo.
- Click Next to continue.
- Verify the user information then click Finish to create the user account.
- Log in to Access Manager as amadmin and assign services to those users as described previously in To Add Services to the Lower Level Organization or in To Add Services to User Accounts.
Configuring a Portal Server User
If you already configured Portal Server for proxy authentication, you do not need to perform steps in this section. Instead, skip to Logging in From a Mobile Device.
The Communication Services channel providers and the Mobile Access wireless applications are intended to give a portal user, through either an HTML or wireless Desktop, access to various services such as Mail, Calendar, and Addressbook. In the default Communication Services channel and Mobile Access installation, individual users must configure their channels with the information needed to gain access to a particular messaging service. The information provided by the user applies to both the HTML and wireless desktops.
Note
This section is only applicable to the “old” communications channels. There might be slight deviations with the “new” Communications Express channels.
To Configure the Mail, Calendar, and Addressbook channels
Each end user must perform the following steps:
- In a web browser, open the following URL:
http://wireless.map.beta.com/portal/dt
- Using the LoginProvider channel, enter the user name and password of a previously defined user (see To Create User Accounts by Using Delegated Administrator Console.
- Click Login.
- Once the Desktop appears, proceed with the following steps.
To Configure a Portal User’s Mail Channel
- Look for the channel named Mail.
The name of the channel is on the left side of the channel’s menu bar.
- On the right side of the channel’s menu bar, click the pencil icon (Edit Mail).
- Under the Account Information category, fill in the following fields:
- Server Name: Type the name of the server that provides IMAP service for this user. In this example, use wireless.map.beta.com.
- IMAP Server Port: If the IMAP server is configured in a standard fashion, skip this field. Otherwise, type the port number of the IMAP service. In this example, use 143.
- SMTP Server Name: If the SMTP server is the same as the IMAP server, skip this field. Otherwise, type the name of the SMTP server that this user should use. In this example, use wireless.map.beta.com.
- Client Port: Type the port number of the IMAP server that provides Messenger Express service. In this example, use 2080.
- User Name: Type the user’s IMAP username.
- User Password: Type the user’s IMAP password.
- When done entering information, click the Finished button.
The Desktop should reappear, but this time the Mail channel should contain a summary of the user’s IMAP inbox.
To Configure a Portal User’s Addressbook Channel
- Look for the channel named Addressbook.
The name of the channel is on the left side of the channel’s menu bar.
- On the right side of the channel’s menu bar, click the pencil icon (Edit Addressbook).
- Under the Account Information category, fill in the following fields:
- Click the Finished button.
The Desktop should reappear, but this time the Addressbook channel should contain a summary of the user’s address book.
To Configure a Portal User’s Calendar Channel
- Look for the channel named Calendar.
The name of the channel is on the left side of the channel’s menu bar.
- On the right side of the channel's menu bar, click the pencil icon (Edit Calendar.)
- Under the Account Information category, fill in the following fields:
- Server Name: Type the name of the server that provides calendar service for this user. This is assumed to be Calendar Server host. In this example, use wireless.map.beta.com.
- Server Port: Type the port number on which Calendar Server services are found. In this example, use 3080.
- User Name: Type the user’s Calendar Server user name.
- Click the Finished button.
The Desktop should reappear, but this time the Calendar channel should contain a summary of the user’s calendar.
Logging in From a Mobile Device
This section describes how to log in to Mobile Access.
To Log In to Mobile Access
Logging in from the Portal Server Desktop is similar. All channels should be readily viewable.
Known Issues and LimitationsSee the Java Enterprise System Release Notes Collection at the following URL to find out about known problems:
How to Report Problems and Provide FeedbackIf you have problems with Sun Java Enterprise System, contact Sun customer support using one of the following mechanisms:
- Sun Software Support services online at
http://www.sun.com/service/sunone/softwareSo that we can best assist you in resolving problems, please have the following information available when you contact support:
- Description of the problem, including the situation where the problem occurs and its impact on your operation
- Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
- Detailed steps on the methods you have used to reproduce the problem
- Any error logs or core dumps
Sun Welcomes Your CommentsSun is interested in improving its documentation and welcomes your comments and suggestions.
To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the title of this book is Sun Java Enterprise System 2005Q1 Technical Note: Deploying Java Enterprise System on a Single Host for Evaluation, and the part number is 819-2201-10.
Additional Sun ResourcesUseful Sun Java System information can be found at the following Internet locations:
- Sun Java System Documentation
http://docs.sun.com/prod/java.sys- Sun Java System Professional Services
http://www.sun.com/service/sunps/sunone- Sun Java System Software Products and Service
http://www.sun.com/software- Sun Java System Software Support Services
http://www.sun.com/service/sunone/software- Sun Java System Support and Knowledge Base
http://www.sun.com/service/support/software- Sun Support and Training Services
http://training.sun.com- Sun Java System Consulting and Professional Services
http://www.sun.com/service/sunps/sunone- Sun Java System Developer Information
http://developers.sun.com- Sun Developer Support Services
http://www.sun.com/developers/support- Sun Java System Software Training
http://www.sun.com/software/training- Sun Software Data Sheets
http://wwws.sun.com/software
Copyright � 2005 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
SUN PROPRIETARY/CONFIDENTIAL.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
Use is subject to license terms.
This distribution may include materials developed by third parties.
Portions may be derived from Berkeley BSD systems, licensed from U. of CA.
Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.
Copyright � 2005 Sun Microsystems, Inc. Tous droits r�serv�s.
Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plusieurs des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et un ou des brevets suppl�mentaires ou des applications de brevet en attente aux Etats - Unis et dans les autres pays.
Propri�t� de SUN/CONFIDENTIEL.
L'utilisation est soumise aux termes du contrat de licence.
Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.
Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.
Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.