This deployment example contains the following sections:
- Summary of Changes
- About This Deployment Example
- Installing the Example
- Configuring Components
- Starting and Stopping Communications Services
- Accessing Sun Resources Online
Summary of Changes
The following describes the changes that have occurred from the Sun Java System Communications Services 6 2005Q4 single host installation example (as described in Deployment Example: Sun Java Communications Services 2005Q4 on a Single Host):
- Portal Server is no longer installed.
- Solaris™ Operating System (OS) 10 is used.
- Hosted domains are now configured.
- All Communications Express UI rendering elements are now deployed in the same web container to support Single Sign-On. As a result, Access Manager is no longer required for Communications Express and there are fewer configuration settings that you have to enter
About This Deployment Example
This 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 Sun Java Communications Suite 5. These instructions are merely intended to guide the evaluator through an initial installation.
What Components Are Installed?
This example guides you through installing the following Communications Suite and Java Enterprise System components:
- Sun Java System Messaging Server 6.3
- Sun Java System Calendar Server 6.3
- Sun Java System Communications Express 6.3
- Sun Java System Directory Preparation Tool 6.4
- Communications Services Delegated Administrator 6.4
- Sun Java System Web Server 7.0
- Sun Java System Message Queue 3.7 UR1
- Sun Java System Access Manager 7.1
- Sun Java System Directory Server Enterprise Edition 6.0
- All Shared Components
The example installation in this document uses the following data that you change according to your installation and test machine:
Recommended Ports
For convenience, this example uses a set of recommended ports. If you use different ports, be sure to make the changes consistently throughout the installation. For example, this document uses port 8800 for the Web Server admin port. If you decide to use port 3333 instead, be sure to change it everywhere 8800 occurs in the deployment example.
Note
Unless otherwise indicated, all of the examples and instructions in this document assume that you are logged in as root.
Implementation Specifications for This Example
This section describes implementation specifications for this example.
Table 3 Client Software Requirements
Component
Platform Requirement
Browser
Netscape™ Communication 7.1, Internet Explorer 6.0 sp4+, or Mozilla™ 1.7.12, Firefox 2.0.3
Summary of Installation and Configuration
Installing and configuring this example involves the following high-level steps:
- Preparing the system for Sun Java Communications Suite
- Running the Java ES installer and selecting the necessary components
- Installing Messaging Server, Calendar Server, Communications Express, Delegated Administrator, Instant Messaging, Web Server, Directory Server, and Access Manager software
- Configuring Delegated Administrator
- Configuring Messaging Server
- Configuring Calendar Server
- Configuring Communications Express
- Configuring users
Installing the Example
This section describes how to install and configure components on multiple systems for evaluation purposes. Some 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:
- 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 Sun Java Communications Services Zip Files
Installing the Components
You install Communications Suite components by running the Java Enterprise System installer.
To Start the Installer
- Log in as root to the machine on which you are installing Communications Suite software.
- Change to the JCS5 directory where you stored and unzipped the Communications Suite zip files.
- Change to the sun_java_commsuite5 directory
- Change to the Solaris_x8 platform directory.
- Start the Java Enterprise System installer in graphical mode.
./installer
- Click Next at the Welcome page.
- Accept the license.
- Select the Upgrade existing software radio button then click Next to continue.
- Select the following products then click Next:
- Click Next to upgrade shared components.
- The installer verifies system requirements. When the installer finishes, click Next.
The installer displays the Ready to Upgrade window.
- Click Next.
- Deselect the registration checkbox then click Install.
The upgrade begins. When the upgrade finishes, the Installation Complete page appears.
- Click Close to exit the installer.
- Restart the Java Enterprise System installer in graphical mode.
./installer &
- Click Next at the Welcome page.
- Accept the license.
The Choose to Upgrade window appears.
- Select the Install new software radio button then click Next to continue.
- Select the following products then click Next to Continue
- on mail.abc.beta.com select the following components:
- Sun Java System Messaging Server 6.3
- Sun Java System Calendar Server 6.3
- Sun Java System Message Queue 3.7 UR1
- on am.abc.beta.com select the following components:
- Sun Java System Communications Express 6.3
- Communications Services Delegated Administrator
- Sun Java System Web Server 7.0
- Sun Java System Access Manager 7.1 (only the required software; no Client SDK)
- on ds.abc.beta.com select the following components:
- Sun Java System Directory Server Enterprise Edition 6.0 (Core, Control Center, Command-Line Utility)
- Sun Java System Directory Preparation Tool 6.4
- on all systems select:
- All Shared Components
- Some versions of Solaris require that the Java SE SDK be upgraded prior to installation. If you are prompted to upgrade the Java SE SDK, choose the default selection to automatically upgrade the SDK to the version included with the installer. Then click Next to continue.
- Click Next to upgrade shared components.
- Specify the installation directories.
Locations:
- Directory Preparation Tool: /opt/SUNWcomds
- Directory Server: /opt/SUNWdsee
- Access Manager: /opt (will create /opt/SUNWam)
- Web Server: /opt (will create /opt/SUNWwbsvr7)
- Web Server Instance: /var/opt/SUNWwbsvr7
- Messaging Server: /opt/SUNWmsgsr
- Calendar Server: /opt (will create /opt/SUNWics5)
- Delegated Administrator: /opt/SUNWcomm
- Communications Express: /opt/SUNWuwc
- Accept the target directories for each product and click Next.
- The installer verifies system requirements, such as memory, disk space, and operating system patches. When done click Next.
- Choose Configure Now then click Next.
- The installer lists the components that must be configured after installation. This document informs you of the order in which to do so.
- Click Next to configure the remaining components. You configure these components as part of the installation process.
Continue with the following procedures to input the appropriate information for each of these products when prompted by the installer.
To Select Common and Web Server Settings
This installation assumes the use of Sun Java System Web Server. You can choose an alternate web container but that is beyond the scope of this document.
- In the Account Preferences Panel, you are asked whether or not you want to use your UserID and Password information for all administrator accounts, or if you want to provide administrator account information for each component.
Choose the All Administrator Accounts option and type admin for the Administrator User ID and adminpass for the Administrator Password then click Next.
- 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 Access Manager Settings
- The following table shows how to respond to the Access Manager configuration options.
To Install the Software
To Verify the Installation
Once the installation has completed, start LDAP and verify that it works.
- 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:web-server-port/amconsole
In this example, type:
http://am.abc.beta.com/amconsole
Use amadmin and adminpass as the user ID and password.
- After verifying that you can log in to the Access Manager console, log out.
- Proceed to Configuring Components for instructions on how to configure Communications Suite components.
Uninstalling the Components
After you complete your evaluation, you can use the Java Enterprise System uninstaller to remove the components that you installed. See the Sun Java Enterprise System 5 Installation Guide for UNIX:
Configuring Components
This section describes how to configure and start the components that you use in this example 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. The mailsrv user is used in Configuring Messaging Server.
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 2).
Type the following commands to create the user mailsrv with a user ID of 7633, a group ID of mail, and a user home directory of /export/home/mailsrv on mail.abc.beta.com host. (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
- Run the comm_dssetup.pl script on ds.abc.beta.com:
cd /opt/SUNWcomds/sbin
/usr/bin/perl comm_dssetup.pl
- Type y to continue.
The perl script prompts for a series of options. The following table shows how to respond to the prompts.
- Confirm your choices and type y to continue. The comm_dssetup script proceeds.
- When prompted, type y to continue with script.
Continue with the next section after the comm_dssetup script finishes and displays its “Successful Completion” message.
Configuring Delegated Administrator and Communications CLI
This section describes configuring Delegated Administrator console and utility, which provide user management.
To Configure Delegated Administrator
- Run the configurator script on am.abc.beta.com:
cd /opt/SUNWcomm/sbin
./config-commda
- Click Next in the Welcome window.
- Accept the default for the Directory to store User Mgmt data files: [/var/opt/SUNWcomm]
If the directory does not exist, click Create Directory to create the directory.
- 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.
The script begins to run.
- When the panel displays “All Tasks Passed,” 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 services in the domain. The next steps correct these problems.
- Click Close to complete the configuration.
- Restart Web Server:
cd /var/opt/SUNWwbsvr7/https-am.abc.beta.com/bin
./stopserv
./startserv
- Modify the mail and calendar domains, and create users by using the commadmin utility:
Create as many users as you need. Steps later in this document show how to add Presence and Instant Messaging services to those users.
Configuring Messaging Server
This section describes configuring Messaging Server, including configuring the Webmail port.
To Configure Messaging Server
- Run the Messaging Server configure script on mail.abc.beta.com:
cd /opt/SUNWmsgsr/sbin
./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: [mail.abc.beta.com]
- Directory to store config/data files: [/var/opt/SUNWmsgsr]
When prompted, choose to create the new directory.
- Install MTA, Message Store, and Webmail Server. 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:
Table 9 Values for Messaging Server configure Script
Option
[Default Value]
Enter:
User/Group Server LDAP
[ldap://ds.abc.beta.com:389]
accept default
Bind As
[cn=Directory Manager]
accept default
Password
--
adminpass
Postmaster email address
--
alvin@abc.beta.com
Password for Messaging Server accounts
--
adminpass
Default email Domain
[abc.beta.com]
accept default
Organization DN
[o=abc.beta.com,o=beta.com]
accept default
- Click Next, then click Configure Now.
You will receive an error about the Webmail port being in use. Click OK to acknowledge this message. The configuration begins. The following step corrects the Webmail port problem.
- When the configuration is finished, click Next to continue, then click Close to exit.
Note
You might observe a failure such that not all the messaging configuration tasks have passed. If this is the case, rerun the Messaging Server configuration script by repeating all the steps above. When prompted for the directory to store configuration or data files, use the same directory as before. A popup window will state that this directory already exists. Click Accept Anyway to verify that the same directory will be used.
- (Option)Configure the Webmail port:
/opt/SUNWmsgsr/sbin/configutil -o service.http.port -v 8080
- Start Messaging Server:
/opt/SUNWmsgsr/sbin/stop-msg
/opt/SUNWmsgsr/sbin/start-msg
- Continue with the next section to configure Calendar Server.
Configuring Calendar Server
This section shows you how to run the Calendar Server configuration script and how to verify the Calendar Server configuration.
To Configure Calendar Server
- Run the Calendar Server configurator script on mail.abc.beta.com:
cd /opt/SUNWics5/cal/sbin
./csconfigurator.sh
- Click Next at the Welcome page.
- The installation script prompts for a series of options. Use the following table to respond to the configuration options:
Table 10 Values for Calendar Server csconfigure Script
Option
[Default Value]
Enter:
LDAP Server Host Name
[ds.abc.beta.com}
accept default
LDAP Server Port
[389]
accept default
Directory Manager DN
[cn=Directory Manager]
accept default
Directory Manager Password
--
adminpass
Enable Virtual Domains support
[Checked]
accept default
Virtual Domains setting: Default domain
[abc.beta.com]
accept default
Calendar Administrator Username
[calmaster]
accept default
Calendar Administrator Password
--
adminpass
Calendar Administrator Email address
[calmaster@abc.beta.com]
accept default
Site administrator
[Yes]
accept default
Set up a Front End/Back End deployment
[Unchecked]
accept default
Email Alarms
[Enabled]
accept default
Administrator Email Address
[calmaster@abc.beta.com]
accept default
SMTP Host Name
[mail.abc.beta.com]
accept default
Service Port
[80]
3080
Maximum Sessions
[5000]
accept default
Maximum Threads
[20]
accept default
Number of server processes
[1]
accept default
Runtime User ID
[icsuser]
accept default
Runtime Group ID
[icsgroup]
accept default
Start Calendar Server after Successful Configuration
[Unchecked]
accept default
Start Calendar Serve on System Startup
[Checked]
Unchecked
Configuration Directory
[/etc/opt/SUNWics5/config]
accept default
Database Directory
[/var/opt/SUNWics5/csdb]
accept default
Attachment Store Directory
[/var/opt/SUNWics5/astore]
accept default
Logs Directory
[/var/opt/SUNWics5/logs]
accept default
Temporary Files Directory
[/var/opt/SUNWics5/tmp]
accept default
Enable Archive
[Checked]
accept default
Archive Directory
[/var/opt/SUNWics5/csdb/archive]
accept default
Enable Hot Backup
[Checked]
accept default
Hot Backup Directory
[/var/opt/SUNWics5/csdb/hotbackup]
accept default
Keep archives for (in days)
[Minimum: 3, Maximum: 6]
accept default
Keep hot backups for (in days)
[Minimum: 3, Maximum: 6]
accept default
Same as archive checkbox
[Checked]
accept default
- Click the Configure Now button to configure Calendar Server.
The Configuration begins and takes less than two minutes.
- Click Next when the configuration is complete.
- 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
- Continue with the next section to configure Communications Express.
Configuring Communications Express
This section shows you how to run the Communications Express configuration script.
To Configure Communications Express
- Run the Communications Express configurator script on am.abc.beta.com:
cd /opt/SUNWuwc/sbin
./config-uwc
- Click Next at the Welcome page.
- Accept the default for Directory to store configuration and data files: [/var/opt/SUNWuwc]
Choose to create the directory when prompted.
- Install the Mail and Calendar Components.
The installation script prompts for a series of options. Use the following table to respond to the configuration options:
Table 11 Values for config-uwc Script
Option
[Default Value]
Enter:
Hostname
[am]
accept default
DNS Domain
[abc.beta.com]
accept default
Web Container
[Web Server]
accept default
Web Server Root Directory
[/opt/SUNWwbsvr7]
accept default
Web Server Config Root Directory
[/var/opt/SUNWwbsvr7]
accept default
Web Server Instance Identifier
[am.abc.beta.com]
accept default
Virtual Server Identifier
[am.abc.beta.com]
accept default
HTTP Port
[80]
accept default
Administration Server Port
[8800]
accept default
Administrator User ID
[admin]
accept default
Administrator Password
--
adminpass
Secure Administration Server Instance
[Unchecked]
accept default
Web Container User ID
[webservd]
accept default
Web Container Group IP
[webservd]
accept default
URI Path
[/uwc]
Enable Hosted Domain Support
[Unchecked]
Checked (Yes)
URL of Directory Server
[ldap://wireless.comms.beta.com:389/]
ldap://ds.abc.beta.com:389/
Bind DN
[cn=Directory Manager]
accept default
Password
--
adminpass
DC Tree suffix
[o=beta.com]
accept default
Default Domain
[abc.beta.com]
accept default
Enable Access Manager for Single Sign-On
[Unchecked]
accept default (not enabled)
Webmail Server Host Name
[wireless.comms.beta.com]
mail.abc.beta.com
Webmail Server Port Number
--
80
Enable login in secure mode
[Unchecked]
accept default (not secure)
Webmail Server SSL Port Number
--
Leave blank
Webmail Admin User ID
--
admin
Admin Password
--
adminpass
Calendar Server Hostname
[wireless.comms.beta.com]
mail.abc.beta.com
Calendar Server Port
[9004]
3080
Calendar Admin User ID
[calmaster]
accept default
Calendar Administrator User Password
--
adminpass
URL of PAB Directory Server
[ldap://ds.abc.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 to continue.
The system displays a message to restart the Web Server instance.
- Click OK.
- Click Next to continue.
- Click Close to quit the Communications Express configurator script.
- Restart Web Server:
cd /var/opt/SUNWwbsvr7/https-am.abc.beta.com/bin
./stopserv
./startserv
Verifying the Configuration
This section describes how to verify the 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://am.abc.beta.com/mail
- Log in as one of the users created earlier.
If you created a user according to the previous steps, type alvin for the user name, and demo for the password.
- In your web browser, open the following URL for Delegated Administrator:
http://am.abc.beta.com/da/DA/Login
Log in as user admin. The password is adminpass.
- Continue with the next section to configure Access Manager.
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 (if you add Portal Server to this deployment at a later date).
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 abc.beta.com -p 80 -w adminpass -W demo -X am.abc.beta.com -S mail,cal -E demo1@abc.beta.com -H mail.abc.beta.com
/opt/SUNWcomm/bin/commadmin user create -D admin -F Demo -l demo2 -L Two -n abc.beta.com -p 80 -w adminpass -W demo -X am.abc.beta.com -S mail,cal -E demo2@abc.beta.com -H am.abc.beta.com
/opt/SUNWcomm/bin/commadmin group create -D admin -G Demostaff -n abc.beta.com -p 80 -w adminpass -X am.abc.beta.com -S mail -E Demostaff@abc.beta.com -H mail.abc.beta.com -o calmaster -m demo1 -m demo2
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:
Prior to using Delegated Administrator, check the resource.properties file to make sure users will be created using options consistent with your usage. Because this example uses a hosted domain scenario, you do not need to edit this file to make changes. If you do want to make changes, perform the following steps.
- Change directories to /var/opt/SUNWcomm/WEB-INF/classes/sun/comm/cli/server/servlet and edit the resource.properties file on am.abc.beta.com.
The default settings for servicepackage refresh rates are as follows:
servicepackage-ttlhours=5
servicepackage-ttlminutes=0
These settings establish the time between refreshes of service packages. In a demo scenario, service packages do not change very often so there is no need to refresh them every five minutes. Instead, they are refreshed every five hours. This improves Delegated Administrator performance. If you later decide to change the refresh rate, for example, to 20 hours, then make this change:
servicepackage-ttlhours=20
The default setting for calendar ID type is set using the switch-caltype variable as follows:
switch-caltype=hosted
The caltype can either be hosted or legacy. When you set caltype to hosted, users are created as uid@domain rather than uid, when you use Delegated Administrator to create them.
- The first time you use Delegated Administrator console, you must add service packs to the organization that contains your users. In a web browser, open the URL for the Delegated Administrator console and log in as amadmin (password is adminpass):
http://am.abc.beta.com/da/DA/Login
- Click the check box next to the comms.beta.com organization, then click the Allocate Service Package button.
The Allocate Service Package window appears. Service packages are organized within a set of three pages.
- Click the Single Page button (to the right of the Compare button) to map the three pages into a single page view.
- Select the desired service packages.
Choose from among earth, mars, mercury, and venus, because they have mail and calendar services enabled. Each service package has a different mail quota.
- Click Next to continue.
- Accept the Mail Service defaults, then click Next.
- If you chose a service package that contains Calendar, type the Calendar Host wireless.comms.beta.com and Anonymous Login Yes. Then click Next.
- Select the quantity of each service pack desired then click Next.
A quantity of 100 is adequate for demo purposes.
- Review your choices and click Finish.
The service packages are created.
- Once the service packs have been allocated for the domain, you can now add users to the domain. Click the domain link, comms.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, earth, then click Next.
- Type the email address, for example, demo5@comms.beta.com. Mail Delivery Option should be Local Inbox. Leave the other fields blank.
- Click Next.
- Choose your calendar preferences and pick your preferred timezone. Then 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 verify that the IM and Presence services have been added to the newly created user. If not, assign services to those users as described previously in To Add Services to the Lower Level Organization.
Starting and Stopping Communications Services
This section describes the commands needed to start and stop all the Communications Services.
To Start and Stop Services
You should stop services before attempting to start them.
- To stop all services:
Table 12 Commands to Stop Communications Services
Service
Command
Instant Messaging
/opt/SUNWiim/sbin/imadmin stop
Access Manager
/etc/init.d/amserver stop
Web Server
/var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin/stopserv
Web Server Administrator
/var/opt/SUNWwbsvr7/admin-server/stopserv
Calendar Server
/opt/SUNWics5/cal/sbin/stop-cal
Messaging Server
/opt/SUNWmsgsr/sbin/stop-msg
Directory Server
/opt/SUNWdsee/ds6/bin/dsadm stop /var/opt/SUNWdsee/dsins1
- To start all services:
Table 13 Commands to Start Communications Services
Service
Command
Directory Server
/opt/SUNWdsee/ds6/bin/dsadm start /var/opt/SUNWdsee/dsins1
Messaging Server
/opt/SUNWmsgsr/sbin/start-msg
Calendar Server
/opt/SUNWics5/cal/sbin/start-cal
Web Server Administrator
/var/opt/SUNWwbsvr7/admin-server/startserv
Web Server
/var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin/startserv
Access Manager
/etc/init.d/amserver start
Instant Messaging
/opt/SUNWiim/sbin/imadmin start
Accessing Sun Resources Online
The docs.sun.comSM web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. Books are available as online files in PDF and HTML formats. Both formats are readable by assistive technologies for users with disabilities.
To access the following Sun resources, go to http://www.sun.com:
Wednesday, May 30, 2007
Sun Java Communications Suite 5 on Multi-Hosts
This deployment example describes how to install Sun Java™ Communications Suite 5 software on multi-hosts for a functioning deployment. This document is intended for any evaluator, system administrator, or installation technician who wants to install and evaluate the services delivered by these components.
Subscribe to:
Posts (Atom)
