Creating Commerce Enabled Portal sample portal application

Complete the following steps on your Rational Application Developer 6.0 machine (WebSphere Commerce Developer machine) to create the Commerce Enabled Portal sample Portal application within Rational Application Developer:

  1. Launch Rational Application Developer.
  2. Set up the WebSphere Portal 5.1 Test Environment server environment.
    1. Select Preferences under the Windows menu to open the Preferences window.
    2. Expand the Sever group and select Installed Runtimes.
    3. Select WebSphere Portal v5.1 stub from the server list and click Edit to open the Edit dialog.
    4. In the Edit Server Runtime dialog, change server name to be "WebSphere Portal v5.1", and specify the installed WebSphere Portal and WebSphere Application Server locations from step 1diii. For example, C:\RAD6\Portal51UTE\AppServer and C:\RAD6\Portal51UTE\PortalServer. Click Finish to save your changes.
  3. Create sample B2B portal project (B2C project is similar).
    1. To open the New Project dialog, select File > New > Project. Select Portal Project and click Next. If you are prompted to enable the required "Portal Development" capability, click OK
    2. Specify a project name (for example, B2BPortal). Click Show Advanced to verify that the default settings are correct. Click Finish.
    3. Switch to the Web perspective, from the left pane (Project Explorer view), right click on the newly created project under Dynamic Web Projects category, and choose Import
    4. In the Select page, select File System and click Next.
    5. In the From directory field, enter the temp\Portals\B2BPortalProject directory.
    6. Check B2BPortalProject and click Finish to overwrite the existing ibm-portal-topology.xml file. Click Yes to overwrite the existing ibm-portal-topology.xml file when prompted. If you are not prompted to overwrite the file, please make sure that you have highlighted the project specified in step 3 to start the import process. Re-do the import if necessary.
  4. Create a sample B2B portlet project.
    1. Select File > New > Project to open the New Project dialog. Select Portlet Project and click Next.

      Note: Do not select the JSR168 project.

    2. Specify a project name (for example, B2BPortlet). Uncheck Create a portlet and click Show Advanced to expand more options, from the drop down list of EAR project. Select the second choice (for example, B2BPortalPortletsEAR).
    3. Click Finish to create a new portlet project.
    4. Switch to Web perspective, from the left pane (Project Explorer view). Find and expand the newly created portlet project under Dynamic Web Projects category. Select WebContent and choose Import.
    5. In the Select page, select File System and click Next.
    6. In the From directory field, enter the temp\Portals\B2BPortletApp directory.
    7. Check B2BPortletApp and click Finish to overwrite the existing portlet.xml and web.xml files. Click Yes twice to overwrite the existing portlet.xml and web.xml files if prompted. If you are not prompted to overwrite the files, please make sure that you have highlighted the WebContent directory specified in step 4 to start the import process. Re-do the import if necessary.
  5. Define the WebSphere Portal 5.1 Test Environment test server and launch the sample B2B portal application.
    1. From the Project Explorer view, right click on the B2B Portal project (for example, B2BPortal). Select Run > Run on Server.
    2. In the Server Selection dialog, select Manually define a server. Select WebSphere Portal v5.1 Test Environment from the server type list. Check Set server as project default and click Finish.
    3. Click OK if you are prompted to repair the server configuration.
    4. After server starts, you should see the sample B2B portal store. Enter a WebSphere Commerce user ID to log in (for example, wcsadmin).

Note: Single sign on is not supported in the WebSphere Commerce development environment. In addition, user and user group permissions are not preset in the WebSphere Commerce development environment; any WebSphere Commerce user can log in and see both the Buyer Organization and Seller Organization pages, but they may not be authorized to view portlet contents based on their different WebSphere Commerce roles.

Feedback