Home
Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ Transaction Server product, from installation and deployment to operating and customization.
Securing
These topics describe the security features of Commerce+ Transaction Server and how to configure these features.
Quick reference to user IDs, passwords, and Web addresses
Administration in the Commerce+ Transaction Server environment requires a variety of user IDs. These user IDs along with their requisite authorities are described in the following list. For the Commerce+ Transaction Server user IDs, the default passwords are identified.
Resetting accounts
If an Commerce+ Transaction Server account gets locked or disabled for some reason, an administrator can unlock or enable the account.

Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ Transaction Server product, from installation and deployment to operating and customization.
- Overview
  Welcome to the HCL Commerce+ Transaction Server overview. Explore these feature overviews to learn how Commerce+ Transaction Server operates. Refer to the related links listed at the end of each topic to access expanded product documentation.
- Deploying
  This section provides details on deploying HCL Commerce+ Transaction Server. It explains how to download the Docker images and Git bundles that comprise the product, how to create a minimal environment, and how to plan for a full deployment. It details supported software versions, patches, and configurations to ensure the platform performs well.
- Migrating
  The following topics show how to migrate an existing HCL Commerce Version 9.1 environment to Commerce+ Transaction Server.
- Operating
  The topics in this section focus on tasks that are performed by business users, marketers, and customer support representatives to connect with partners and attract and satisfy customers.
- Administering
  The site administrator performs the tasks needed to support day to day operations of the Commerce+ Transaction Server site.
- Extending
  Using Commerce+ Transaction Server's xC programming model, you can use HCL-provided extension points to extend existing Commerce logic. You can implement these extensions with the xC Customization toolkit provided by HCL. Commerce+ also provides Packaged Business Capability integrations that extend the product's reach and functionality.
- Securing
  These topics describe the security features of Commerce+ Transaction Server and how to configure these features.
  - Non-applicable security vulnerabilities
    The Commerce+ Transaction Server team has evaluated the following security vulnerabilities identified within the Commerce+ Transaction Server stack and determined there is no impact to default deployments.
  - Commerce+ Transaction Server security model
    Authentication is the process of verifying that users or applications are who they claim to be. In an Commerce+ Transaction Server system, authentication is required for all users and applications that access the system, except for guest customers.
  - Commerce+ Transaction Server authentication model
    The Commerce+ Transaction Server authentication model is based on the following concepts: challenge mechanisms, authentication mechanisms and user registries.
  - Authorization
    Commerce+ Transaction Server views access control or authorization as the process of verifying that users or applications have sufficient authority to access a resource. This section describes the details of several aspects of Commerce+ Transaction Server access control.
  - Hardening site security checklist
    To harden the security of your HCL Commerce site, you can enable and configure various security features. In addition, site customizations must always be made to comply with best practices as outlined in this document.
  - Site security considerations
    To enhance the security of your Commerce+ Transaction Server site, you can enable various features in Administration Console or in the Commerce+ Transaction Server configuration file.
  - Session management
    Browsers and e-commerce sites use HTTP to communicate. HTTP is a stateless protocol, which means that each command is run independently without any knowledge of the commands that came before it. Because it is a stateless protocol, sessions must be managed between the browser side and the server side.
  - Quick reference to user IDs, passwords, and Web addresses
    Administration in the Commerce+ Transaction Server environment requires a variety of user IDs. These user IDs along with their requisite authorities are described in the following list. For the Commerce+ Transaction Server user IDs, the default passwords are identified.
    - Changing database passwords
      You can change database user passwords (DBUserPwd) and database administrator passwords (DBAPwd) by updating the Commerce+ Transaction Server configuration file and updating properties in the WebSphere Application Server administrative console.
    - Setting your Apache HTTP Server administrator password
      You can set your Apache HTTP Server administrator password.
    - Changing the SSL key file password
      If you are using Apache HTTP Server, follow these steps to change your SSL key file password.
    - Generating Commerce+ Transaction Server encrypted passwords
      You can generate encrypted passwords in order to manually reset the password of a user from a command line. There are other tools (such as the ResetPassword command) that accomplish the same task. To manually reset the password, the administrator would take the encrypted password that is output by the utilities and update the LOGONPASSWORD field of the USERREG table. The administrator would also update the SALT field of the USERREG table with the chosen salt.
    - Resetting accounts
      If an Commerce+ Transaction Server account gets locked or disabled for some reason, an administrator can unlock or enable the account.
      - Resetting a Site Administrator's account
        If an Commerce+ Transaction Server account gets locked or disabled for some reason, an administrator can unlock or enable the account.
      - Resetting non-Site Administrator accounts
        Resetting user accounts that are not a Site Administrator account
      - Resetting the wcsadmin user password
        Resetting the wcsadmin user account password in the toolkit environment.
      - Resetting the wcsadmin user password (runtime)
        You can reset the default wcsadmin user password (by calling wcs_password).
      - Enabling password reset messages
        You can enable a message to notify users when they change their passwords.
    - LDAP server password storage consideration
      If you have chosen to use LDAP as your user registry, you should decide how you want your passwords to be stored. Many LDAP servers will provide options for encrypting or hashing the passwords, and sometimes even allow the passwords to be stored in plain text. Although the decision on how to store the password has no impact on the integration with Commerce+ Transaction Server, you should investigate your settings and ensure that they comply with your security requirements. For information about configuring your LDAP server, refer to the product documentation provided with your LDAP server.
- Performance
  Topics in the Performance section describe the means by which to plan, implement, test, and re-visit the optimization of Commerce+ Transaction Server site performance.
- Troubleshooting
  Topics in the Troubleshooting section highlight common issues that are encountered with Commerce+ Transaction Server, and how they can be addressed or mitigated.
- Reference
  Topics in the Reference section contain all of the Commerce+ Transaction Server reference documentation.

Resetting accounts

If an Commerce+ Transaction Server account gets locked or disabled for some reason, an administrator can unlock or enable the account.