WebSphere Commerce Developer

WebSphere Commerce development environment

WebSphere Commerce Developer is the development toolkit for customizing a WebSphere Commerce application.

You should use the edition of WebSphere Commerce Developer that matches your edition of WebSphere Commerce:

  • WebSphere Commerce Enterprise WebSphere Commerce Enterprise and WebSphere Commerce Developer Enterprise
  • WebSphere Commerce Professional WebSphere Commerce Professional and WebSphere Commerce Developer Professional
  • WebSphere Commerce - Express WebSphere Commerce - Express and WebSphere Commerce Developer Express

All of the WebSphere Commerce Developer editions include the tools you require to create customized code and perform Web development tasks. In general, this documentation set refers to these products collectively as the WebSphere Commerce development environment.

The WebSphere Commerce development environment builds on top of Rational Application Developer, which is the core development environment from IBM. It helps you optimize and simplify Java 2 Platform Enterprise Edition and Web services development by offering best practices, templates, code generation, and the most comprehensive development environment in its class. This integrated development environment (IDE) includes integrated support for Java components, enterprise beans, servlets, JSP files, HTML, XML, and Web services all in one development environment.

There are four main components to the WebSphere Commerce development environment:

  1. The WebSphere Commerce workspace used within Rational Application Developer
  2. The development database
  3. WebSphere Commerce tools and plug-ins for Rational Application Developer
  4. File system assets, such as WebSphere Commerce XML configuration and properties files

In the WebSphere Commerce development environment, you can create customized code and then test the code using the WebSphere Commerce Test Server.

Note: WebSphere Commerce Developer is configured by default to use the DummyServerKeyFile.jks and DummyServerTrustFile.jks files with the default self-signed certificate. That is, an SSL certificate that is not signed by a trusted certificate authority, but signed by the issuer of the certificate. If you want to have a secure test environment, you must generate your own certificate to replace the dummy certificates. See the WebSphere Application Server Security Guide for more information about the dummy key and trust file certificates and how to replace them. For information about encoding passwords in files, see Encoding password in files