Samples > IBM Sales Center samples: Actions, dialogs, editors and requests


Disable SSL for the IBM Sales Center

This sample demonstrates disabling SSL so that the IBM Sales Center connects to the WebSphere Commerce Server using a non-SSL port. Disabling SSL is useful for instance, if you do not want to use SSL within the development environment.


Make changes to the IBM Sales Center client

In this section, we will create a new plug-in in the IBM Sales Center development environment to contain the new code. Instead of this step of this sample, you can download the completed plug-in and import it into the IBM Sales Center development environment.

  1. Open the IBM Sales Center development environment.

  2. Create a new plug-in called disableSSL.

  3. In the plug-in, leave the default dependencies and add the com.ibm.commerce.telesales.config as a new dependency. You should have three dependencies:

    • org.eclipse.ui

    • org.eclipse.core.runtime

    • com.ibm.commerce.telesales.config

  4. Add an extension to the org.eclipse.ui.startup plug-in. You can use the plug-in editor interface, or edit the plug-in.xml file directly. The resulting code should look similar to the following: <extension point="org.eclipse.ui.startup"> </extension>

  5. In the disableSSL plug-in project, navigate to the disableSSL package and open the DisableSSLPlugin.java file for editing.

  6. Add the following import statements:

    • import com.ibm.commerce.telesales.config.ConfigPlugin;

    • import com.ibm.commerce.telesales.config.IConfigConstants;

    • import org.eclipse.ui.IStartup;

  7. Modify the class signature to implement the IStartup class. The complete class signature should look like the following: public class DisableSSLPlugin extends AbstractUIPlugin implements IStartup.

  8. Add the following method at the end of the class : public void earlyStartup() { ConfigPlugin.getPlugin().getPreferenceStore().setValue(IConfigConstants.PREF_SSL_ENABLED, false); }


Make changes to the WebSphere Commerce Server

On the WebSphere Commerce Server, ensure that the Enablement-BusinessContextWebServicesRouter and Telesales-BaseWebServicesRouter web modules use a non-SSL port. In this sample, VH_ instance will be used as the non-SSL port. By default, the non-SSL port number is 80. This step is not required if the IBM Sales Center does not connect to the WebSphere Commerce Server directly; for example if the IBM Sales Center uses a non-SSL connection to a proxy server, then uses an SSL connection between the proxy server and WebSphere Commerce.

To change the Enablement-BusinessContextWebServicesRouter and Telesales-BaseWebServicesRouter web modules ports, we will change the virtual host settings then generate a new plugin-cfg.xml file:

  1. Launch the Administration Console for the profile. See the Starting the WebSphere Application Server Administrative Consoletopic in the WebSphere Application Server information center for more information.

  2. In the Administration Console navigate to Applications > Enterprise Applications.

  3. Click WC_ instance .

  4. In the Additional Properties list click Map virtual hosts for Web modules.

  5. Change the Virtual host name for the Enablement-BusinessContextWebServicesRouter and Telesales-BaseWebServicesRouter web modules to VH_ instance .

  6. Click OK.

  7. Click Save and Save again to save to the master configuration. For more information see the Mapping virtual hosts for Web modules topic in the WebSphere Application Server information center.

  8. Regenerate the plugin-cfg.xml file:

    1. In the WebSphere Application Server, click Servers > Web Servers.

    2. Select the Web Server and click Generate Plug-in.

  9. Restart the WC_ instance application, by clicking Applications > Enterprise Applications, selecting WC_ instance then clicking Stop then Start.

  10. If necessary, restart the web server to pick up the new plugin-cfg.xml file. Some web servers will automatically pick up plugin-cfg.xml file changes, depending on the settings.


Test the changes

To test the changes, launch the IBM Sales Center and connect to the WebSphere Commerce server using the non-SSL port:

  1. To test the changes, click Run > Run.

  2. From the Configurations list, select Sales Center.

  3. In the Arguments tab, select Clear workspace data before launching.

  4. Click Run.

  5. When asked if you really want to clear the workspace data, click Yes.

  6. When the IBM Sales Center client opens, click Application > Open > IBM Sales Center - Order Management.

  7. Click File > Logon.

  8. Click the Connectivity button.

  9. In the Server field, enter the fully-qualified hostname of the WebSphere Commerce Server.

  10. In the HTTPS Port field, enter the port you configured on the WebSphere Commerce Server for the Enablement-BusinessContextWebServicesRouter and Telesales-BaseWebServicesRouter web modules to use non-SSL. In this sample, that port is 80.

  11. Click OK.

  12. In the logon dialog, enter a valid user name and password and click OK. You should be able to connect to the WebSphere Commerce server.

  13. To open the IBM Sales Center using SSL, follow the same directions as above but deselect the disableSSL plug-in in the Run dialog before opening the Sales Center client.


Deploy the changes

Deploy the changes to a production server by following instructions in Deploying customizations to the IBM Sales Center. To create or update a feature, see Deployment step of the Customizing the appearance of the IBM Sales Center tutorial.


Related concepts

Overview of customizing IBM Sales Center


+

Search Tips   |   Advanced Search