You can deploy your Flex applications on portal servers that have a full LiveCycle Data Services ES web application installed, and portal servers that do not have a LiveCycle Data Services ES web application but host a set of precompiled SWF files.

Deploying with a LiveCycle Data Services ES web application

When a Flex application is in a LiveCycle Data Services ES web application, you have a choice of precompiling it or compiling it at run time. You can also use standard Flex debug and error logging based on the debug level that you set in services-config.xml.

1. Copy flex-portal.jar from the installation_dir\resources\wsrp\lib directory to the WEB-INF\lib directory of your web application.
2. Copy the wsrp-jsp directory from installation_dir\resources\wsrp to the root of your web application.
3. Follow the portal-server-specific steps that follow to create portlets for your Flex applications.

Deploying without a LiveCycle Data Services ES web application

When the exposed Flex applications are not part of a LiveCycle Data Services ES web application, you can only expose precompiled SWF files. You cannot compile your Flex applications at run time or use standard LiveCycle Data Services ES logging because the pieces necessary to support that functionality are inside the LiveCycle Data Services ES web application.

1. Copy flex-portal.jar and flex-messaging-common.jar from installation_dir\resources\wsrp\lib directory to the WEB-INF\lib directory of your web application.
2. Copy the wsrp-jsp directory from installation_dir\resources\wsrp directory to the root of your web application.
3. Follow the portal server specific steps that follow to create portlets for your Flex applications.

Deploying on JBoss Portal

When deploying on JBoss Portal, consult the relevant JBoss documentation, including the following:

• General JBoss WSRP information
• JBoss administration portlet information

Configure a JBoss Portal producer server

1. To create a local portlet, modify the portlet.xml file in the WEB-INF directory of your web application.
2. To create a local instance of the new portlet, either modify portlet-instances.xml in the WEB-INF directory of your web application, or use the administration portlet at
   http://SERVER:PORT/admin.
3. To enable your portlet for WSRP consumption, update jboss-portlet.xml in the WEB-INF directory of your web application (setting the remoteable flag to true), or use the administration portlet http://SERVER:PORT/admin, and select the Remoteable option for your portlet.

   The WSDL for your producer server should be
   http://SERVER:PORT/portal-wsrp/MarkupService?wsdl.

   Depending on how your DNS is set up, it has a server name that is accessible only from within your local network (server name is computer name) or a server name that is accessible from outside the local network (server name is fully qualified or is an IP address). If the SERVER name in the generated WSDL does not appear correctly, you can adjust your DNS settings or manually modify the .wsdl file, for example:

   /server/default/data/wsdl/portal-wsrp.war/wsrp_services.wsdl

Configure a JBoss Portal consumer server

1. Add the WSDL of the producer server (does not have to be a JBoss server) to jboss-portal.sar\portal-wsrp.sar\default-wsrp.xml.
2. Use the administration portlet at http://SERVER:PORT/admin to get a list of available remote portlets.
3. Create instances of any remote portlets that you are interested in.

Deploying on WebLogic Portal

When deploying on WebLogic Portal, consult the relevant WebLogic documentation at
http://e-docs.bea.com/wlp/docs92/index.html, including the following:

• Using WSRP with WebLogic Portal
• Federated Portals Guide
• Portlet Development Guide

Producer server configuration

Create a local portlet by using the WebLogic Workshop IDE and completing the following steps.

Create a local portlet

1. Create a Portal Web Project.
2. Create a portlet (New > Portlet).
3. After naming the portlet, select Java Portlet as the portlet type.
4. Ensure that you set Class Name to flex.portal.GenericFlexPortlet.

Manually configure a portlet

1. Modify WEB-INF/portlet.xml; for more information, see Enabling a portlet.
2. Create a .portlet file for your portlet.
3. Ensure that the portlet-name attribute in the portlet.xml file matches the definitionLabel property in the .portlet file.

Consider the following when configuring a WebLogic Portal producer server:

• The URL of the WebLogic portal administration user interface is http://SERVER:PORT/context-root/Admin/portal.portal.
• WebLogic supports quite a few different portlet types, as described in the WebLogic Portlet Development Guide. Look specifically at "Java Portlets (JSR 168)."
• To use the EDIT mode of a portlet, your users must have sufficient permission access to the PreferencePersistenceManager EJB.
• WebLogic portlets by default are enabled as WSRP producers. To disable a portlet from being WSRP consumable, set its Offer as Remote property to false in the WebLogic Workshop IDE.
• The producer server documentation describes the steps necessary to enable a project as a WSRP producer in the WebLogic Workshop IDE. The WSDL generated for your producer server should be http://SERVER:PORT/context-root/producer?wsdl.

  Depending on your DNS setup, the WSDL either has a server name that is accessible only from within your local network (server name is computer name) or a server name that is accessible from outside the local network (server name is fully qualified or is an IP address). If the SERVER name in the generated WSDL does not appear correctly, you can adjust your DNS settings or manually modify the wsrp-wsdl-full.wsdl file that is generated for your application.

  After setting up your portlet on the producer server, you can use the Portal Management section of the portal administration user interface (http://SERVER:PORT/context-root/Admin/portal.portal) or the WebLogic Workshop IDE to include your Flex application portlet in portal pages.

Consumer server configuration

Complete the following steps to add the WSDL of the remote producer server to the consumer server. The producer server does not have to be a WebLogic server.

1. Go to portal administration application http://SERVER:PORT/context-root/Admin/portal.portal.
2. Go to Portal Management.
3. Browse to Library > Remote Producers.
4. Create an entry for the remote producer.

Your remote portlet appears under the Portlets tab. You can add remote portlets to pages by navigating to the page under the Portals tab.

Deploying on WebSphere Portal 5.1 or WAS 6.0

When deploying a portlet on WebSphere Portal 5.1 or WAS 6.0, consult the relevant WebSphere documentation, including the following:

• Using JSR 168 with WebSphere Portal guide
• Using WSRP services with WebSphere Portal (online help)

Consider the following when deploying on WebSphere Portal:

• The default URL of the WebSphere Application Server is http://SERVER:9080.
• The default URL of the WebSphere Portal administration application is
  http://SERVER:9081/wps/portal.
• The default URL of the WebSphere Application Server administration application is
  http://SERVER:9060/ibm/console/.
• Unlike JBoss Portal and WebLogic Portal, WebSphere Portal is a completely separate server with a different port and context root than the application server.

Producer server configuration

Deploying a portlet on a WebSphere producer server

1. Deploy the WAR file that contains your application logic and portlet deployment configuration (portlet.xml) on the application server using the application server administration application. You should be able to test the non-portlet functionality of your application by starting the application server.
2. Add the same WAR file to the portal server's module list:
   1. Log in to the portal server administration application with admin/admin as the username/password.
   2. Select the Administration tab in the upper-right corner.
   3. Select the Portlet Management tab from the list on the left.
   4. Select Web Modules, and install your WAR file. This adds every portlet configured in your portlet.xml file to the list of portlets available from the portal server.
   5. Verify that your portlets appear under the Portlets tab on the left.

   Now you can create a local portal page with your new portlets.

To make a portlet available as a WSRP producer, click the star icon next to its name under the Portlets tab. A check mark appears in the Provided column for that portlet.

The WSDL of your producer should be
http://SERVER:PRODUCER_PORT/wps/wsdl/wsrp_service.wsdl

Consumer server configuration

Complete the following steps to add the WSDL of the remote producer server to the consumer server. The producer server does not have to be a WebSphere server.

Add the WSDL to the consumer server

1. Select Portlet Management tab on the left side under the Administration tab.
2. Select Web Services.
3. Click the New Producer button to add the producer WSDL.
4. Under the Web Modules tab, look for an entry with the name WSRP Producer (name you gave to remote producer) Application.
5. Navigate to the portlets listed under this application
6. Make copies of any portlets to consume.

Your remote portlets appear under the Portlets tab, and you can add them to your pages.