Home
User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
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.
Common installation and administration tasks
The following tasks are common tasks that you need to perform, often repeatedly, as part of WebSphere Commerce installation and administration duties.
WebSphere Commerce administration tasks
The tasks that are listed on this page provide instructions for common WebSphere Commerce tasks that you might need to complete while administering WebSphere Commerce.
Starting and stopping WebSphere Commerce and its components
Review the following topics for information about how to start and stop WebSphere Commerce and its components.
Starting and stopping WebSphere Commerce
The WebSphere Commerce instance is created and administered within a WebSphere Application Server profile. To start or stop a WebSphere Commerce instance you must start or stop the associated WebSphere Application Server profile.
... on AIX and Linux operating systems
Starting an application server starts both the application server and any applications that run inside the application server.

AIX

Linux

Starting and stopping an application server on AIX and Linux operating systems

Starting an application server starts both the application server and any applications that run inside the application server.

About this task

When starting an application server the application server might start successfully but applications running inside an application server may fail to start. Check the log files for errors.

Procedure

Ensure that your database management system is started.
Do one of the following:
- Issue the following commands in a terminal window:
```
su - WC_non_root_user
cd WC_profiledir/bin
```
- For a WebSphere Application Server Network Deployment manager profile:
```
su - root
cd WAS_ND_profiledir/bin
```
where:

WC_non_root_user

The non-root user ID under which the application server will run.

WC_profiledir

The directory for WebSphere Application Server profile used for WebSphere Commerce.

WAS_ND_profiledir

The directory for WebSphere Application Server profile used for WebSphere Application Server Network Deployment manager profile.
Do one of the following:
- To start an application server, enter:
```
./startServer.sh application_server_name
```
- To stop an application server, enter:
```
./stopServer.sh application_server_name
```
- To start the deployment manager:
```
./startManager.sh
```
- To stop the deployment manager:
```
./stopManager.sh
```
where:
application_server_name is the name of the application server you want to start or stop. The default WebSphere Application Server application server name is server1.
Check the log files for any problems or errors. The log files are located in directory:WC_profileDir/logs/server1
Starting and stopping quick reference. Select the appropriate link from the left pane based on your version of WebSphere Application Server.
Start the IBM Knowledge Center.
The IBM Knowledge Center (local help) must be started in order to provide help when using the WebSphere Commerce tools such as WebSphere Commerce Accelerator.