Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Administering
Overview of administering a WebSphere Commerce site
In WebSphere Commerce the person who performs administrative tasks is called a Site Administrator. The Site Administrator installs, configures, and maintains WebSphere Commerce and the associated software and hardware. The administrator responds to system warnings, alerts, and errors, and diagnoses and resolves system problems. Typically, this person controls access and authorization (creating and assigning members to the appropriate role), manages the Web site, monitors performance, and manages load balancing tasks. The Site Administrator might be responsible for establishing and maintaining several server configurations for different stages of development such as testing, staging, and production. The Site Administrator also handles critical system backups and resolves performance problems.
Administration Console
Site Administrators use the Administration Console to control a site or store by completing administrative operations and configuration tasks such as publishing stores, refreshing the registry, and scheduling jobs. You can access the Administration Console at a site-level, or for a particular store.
Message types
WebSphere Commerce predefines several message types and sets them as active. You can change the parameters for message types.
Configuring validation for No Operation (NOOP) messages
WebSphere Commerce uses SMTP connection pooling by default. SMTPTransport.isConnected() is used for validation before getting a connection from the pool, and sends a No Operation (NOOP) message. Some firewalls might be configured to introduce a delay after receiving several NOOP messages to protect against Denial of Service attacks. You must either validate the firewall and SMTP configurations for NOOP messages, or set mail.smtp.userset to true.

WebSphere Commerce Version 7.0.0.2 or later

Configuring validation for No Operation (NOOP) messages

WebSphere Commerce uses SMTP connection pooling by default. SMTPTransport.isConnected() is used for validation before getting a connection from the pool, and sends a No Operation (NOOP) message. Some firewalls might be configured to introduce a delay after receiving several NOOP messages to protect against Denial of Service attacks. You must either validate the firewall and SMTP configurations for NOOP messages, or set mail.smtp.userset to true.

Perform the following steps to set mail.smtp.userset to true:

Procedure

Create a file named JCAEmailConnectionRequestInfo.properties in the WAS_installdir/lib directory.
Include the following parameter in the file:
```
mail.smtp.userset=true
```
For a list of possible JavaMail configuration parameters, see the package description of Package�com.sun.mail.smtp.
Restart the WebSphere Commerce JVM for the changes to take effect.