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.
Administering
The site administrator performs the tasks needed to support day to day operations of the Commerce+ Transaction Server site.
System Administration
Lab allows you to manage transport, messages, scheduler, Connectors, registries, and security policies.
Message types
Commerce+ Transaction Server predefines several message types and sets them as active. You can create or change the parameters for message types from the Lab Tools.
Delete message type
Use the Lab Tools to delete the message type.

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 explains how to deploy HCL Commerce+ Transaction Server, including downloading the Docker images and Git bundles that make up the product, building a minimal environment for learning and testing, and planning a full production deployment. It also covers the supported software versions, patches, and configurations needed for the platform to perform 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.
  - Member groups
    A member group is a grouping of members - users, organizations, or other member groups - used for various business purposes. Two kinds of member groups exist: implicit and explicit. An implicit member group contains users that share common attributes and are therefore considered members of a specific member group. An implicit member group specifies criteria or attributes that users must satisfy in order to be considered members of that member group. You can also explicitly exclude certain users although they satisfy the criteria. An explicit member group contains explicitly assigned users, who may or may not share common attributes. A member group can be both implicit and explicit at the same time.
  - Inventory management
    Use the HCL Commerce+ Inventory to manage your inventory and access your Inventory Locations (ILs), where your inventory is physically stored and is delivered or shipped from.
  - Approvals
    Accurate, secure transactions require that a second individual approve some electronic marketplace actions before they proceed. This individual, called an approver, can accept or reject requests to perform a specific action. During the organization registration process, the organization administrator selects the business processes for which they want to enable approval. This is done by signing up for the appropriate approval member group during membership registration. The organization administrator also populates the approver member groups. Only users within these groups have the authority to accept or reject requests to perform those actions for which approval has been enabled.
  - System Administration
    Lab allows you to manage transport, messages, scheduler, Connectors, registries, and security policies.
    - Scheduler
      A job is Commerce+ Transaction Server command that is scheduled to run on behalf of a site or store at a specified time or interval. The three types of jobs are: site level jobs, store level jobs, and broadcast jobs.
    - Messages
      Site Administrators can use the resend function in Commerce+ Transaction Server to resend messages that are stored in the Commerce+ Transaction Server system.
    - Transport methods
      Commerce+ Transaction Server provides several transport methods. By default, the e-mail transport method is configured and active. You can also use these transport methods: File, IBM MQ, or a sample adapter. You can configure transport methods for the site, or for particular stores.
    - Message types
      Commerce+ Transaction Server predefines several message types and sets them as active. You can create or change the parameters for message types from the Lab Tools.
      - Creating new message type
        Use the Lab Tools to create new message type.
      - Updating message type
        Use the Lab Tools to update the message type.
      - Search message type
        Use the Tools to search for the message type.
      - Delete message type
        Use the Lab Tools to delete the message type.
      - Refresh message type
        Use the Lab Tools to refresh the message type list.
      - Configuring outbound email notification messages
        Use the Lab Tools to configure outbound email notification messages.
      - Configuring email activity accounts
        To support sending marketing emails for your store, you must use the Lab to configure outbound and inbound email activity accounts.
      - Configuring timeouts for SMTP connections
        Configure timeouts for SMTP connections by indicating specific parameters. By not configuring timeouts, the thread can wait indefinitely for an SMTP server to respond, leading to a hang in the Commerce+ Transaction Server JVM.
      - Configuring a different mail Socket Factory
        If you use a third-party mail service like Amazon Web Services or Microsoft Office 365, you might need to change the Socket Factory to javax.net.SocketFactory.
      - Configuring validation for No Operation (NOOP) messages
        Commerce+ Transaction Server 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.
      - Assigning a message type to a transport method for a site or store
        If you assign a message type to a particular transport, the transport must first be set active. By default, only the e-mail transport is active at the site-level. If the store does not have a message transport assignment, then the site assignment is used.
      - Enabling order status notification
        This message is sent to the administrator with "Recipient" listed under this Administration Console configuration. It will not send to the customer of the order. This message assumes that only the Site Administrator is interested in the order status update. Commerce+ Transaction Server site or store developers can customize the OrderStatusNotifySendCmd command by providing another implementation to send e-mails to either the administrator, or the customer, or both.
      - Enabling transports
        Not all transports are enabled by default. If you need a transport that is not enabled by default, you can enable the transport by enabling the transport from the Lab tools.
      - Enabling the Report_NC_PurchaseOrder message
        The Order Create outbound message can be enabled in either XML format, or the legacy format.
      - Enabling the shipment notification e-mail
        You can configure Commerce+ Transaction Server so that a shipment notification e-mail is sent to customers when their order is shipped:
      - Configuring the Request_WCS_BE_ProductInventory message
        To enable Commerce+ Transaction Server to use the send-receive message service, configure the CheckInventoryAvailabilityBE message.
      - Activating error notification
        After you have set the system default settings for the e-mail transport method you can activate error notification.
      - Outbound messages
        The Commerce+ Transaction Server outbound messaging system can process different message types. Each message type is sent to the messaging system in response to a specific type of event that occurs within the Commerce+ Transaction Server system. You specify the message type and settings in the Lab. The messaging system processes the message according to the type and settings that you specified, such as mail server, server port, sender, and subject. You change the content of the mail by modifying the JSP file that corresponds to the message type.
    - Registries
      The Registries tool allows site administrators to update a registry without requiring a server restart. The Registry Manager maintains a set of registries for catching Commerce+ Transaction Server runtime data. Each registry provides methods to enable adding, deleting, and refreshing of the registry content. These methods are available to the URL interface by using the ListRegistry and the RefreshRegistry commands.
    - Security Policies
      For enhanced security of your site, ensure that you are aware and up to date on all account related policies.
  - Staging environment
    An Commerce+ Transaction Server staging environment is a runtime environment where business and technical users can update and manage store data and preview changes. The changes can then be propagated to the production environment.
  - Workspaces
    Workspaces provide a powerful and flexible way to manage and preview changes to your e-commerce website without affecting the live production environment.
  - Commerce+ Transaction Server database
    As a site administrator, maintain the Commerce+ Transaction Server database and ensure that any Commerce+ Transaction Server utilities and processes that load and retrieve data from the database is configured to connect to the database properly.
  - Dynamic caching
    In general, caching improves response time and reduces system load. Caching techniques are used to improve the performance of World Wide Web Internet applications. Most techniques cache static content (content that rarely changes) such as graphic and text files. However, many websites serve dynamic content, containing personalized information or data that changes more frequently. Caching dynamic content requires more sophisticated caching techniques, such as those provided by the Open Liberty Server dynamic cache, a built-in service for caching and serving dynamic content.
  - Extracting and loading data
    Commerce+ Transaction Server provides utilities for preparing and loading data into a Commerce+ Transaction Server database. The loading utilities are flexible and you can continue to use these utilities when you customize the Commerce+ Transaction Server schema.
  - Administering Search
    HCL Commerce+ Transaction Server Search provides the core search capability for Commerce+ Transaction Server, enabling product indexing and retrieval for customer queries across the storefront. It supports guided navigation, landing pages, and dynamic merchandising, helping shoppers quickly find relevant products while giving merchandisers tools to influence search results.
- 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.
- 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.

Delete message type

Use the Lab Tools to delete the message type.

Procedure

Open Lab Tools, and from the left navigation menu, select Administration > System Administration > Message Types.
In the Search field, enter the Message type or Transport to search the message type for deletion.
From Actions menu, click on Delete icon to delete the message type.