Developing > Persistence layer > WebSphere Commerce integration with WebSphere Portal



Portlet packaging structure

The WebSphere Commerce Portlet is provided as a WAR file for the portal administrator to install to the Portal Server.

These are the major items in this package:

This portlet application requires two deployment descriptors:

Directory structure

The WAR file of the Portlet application has the following directory structure.

Directory Description
/ Root directory of the portlet file structure.
/wsdl Location for cooperative portlet configuration files.
/jsp Location for JSP files.
/WEB-INF Location for all protected resources. The /WEB-INF directory stores the portlet descriptor document and all of the runtime executable JAR files and classes that the packaged portlet requires. The portlet information directory is not part of the public document tree of the application. Files that reside in /WEB-INF are not served directly to a client.
/WEB-INF/config/base Location of all the core and bootstrap configuration files that cannot be customized.
/WEB-INF/config/ext Location of all customizable configuration files.
/WEB-INF/lib Location for storing portlet JAR files, such as component client libraries.
/WEB-INF/classes Location for portlet class files. Individual class files should be stored in a directory structure within /WEB-INF/classes that reflects the class package.
/WEB-INF/classes/nl Location for portlet resource bundles.
/WEB-INF/classes/config Location for WebSphere Commerce service binding configuration files.
/WEB-INF/wsdl Location for WebSphere Commerce service deployment configuration files.
/META-INF Location for the manifest file, manifest.mf. The manifest is in the standard JAR file format as defined by the Java 1.3 specification. Files that reside in /META-INF are not served to clients.

Related concepts


WebSphere Commerce integration with WebSphere Portal

Related tasks


Packaging portlets


Configure the sample portlets in the server environment

Last updated: 25 November 2009