1 Reply Latest reply on Jul 7, 2010 3:00 AM by Karl_Sigiscar_1971

    incorporating blzeds with IBMWebspherev6.1.0 step by step process

    korrapati.kishore

      Hi,

           Any one can suggest BlazeDS configuration in IBMWebspherev6.1.0..

        • 1. Re: incorporating blzeds with IBMWebspherev6.1.0 step by step process
          Karl_Sigiscar_1971 Level 3

          To configure LiveCycle Data Services ES for use with WebSphere:

           

          1. Expand the flex WAR file to a temporary folder:
            jar -xvf flex.war 
          2. Uncomment the resource-ref element for WorkManager in web.xml. This makes the resource available in java:comp/env/ at res-ref-name (java:comp/env/wm/MessagingWorkManager):
            <resource-ref>
                 <description>Flex Messaging WorkManager</description>
                 <res-ref-name>wm/MessagingWorkManager</res-ref-name>
                 <res-type>com.ibm.websphere.asynchbeans.WorkManager</res-type>
                 <res-auth>Container</res-auth>
                 <res-sharing-scope>Shareable</res-sharing-scope>
            </resource-ref>
          3. Map the WorkManager resource-ref in web.xml to the RTMPEndpoint in lcds-webapp-root/WEB-INF/flex/services-config.xml.     The websphere-workmanager-jndi-name maps to the res-ref-name available in java:comp/env in step 2. For example:
            <channel-definition id="my-rtmp" class="mx.messaging.channels.RTMPChannel">
                 <endpoint url="http://{server.name}:2038/" class="flex.messaging.endpoints.RTMPEndpoint"/>
                 <properties>
                   ...
                   <websphere-workmanager-jndi-name>java:comp/env/wm/MessagingWorkManager</websphere-workmanager-jndi-name>
                   ...
                 </properties>
               </channel-definition>

            To configure dataservice destinations that do not use transactions with RTMP based channels, set <use-transactions>false</use-transactions> for the dataservice destination in /WEB-INF/flex/data-management-config.xml.

          4. Create a WAR file from the expanded directory structure. For example:
            jar -cvf flex.war *
          5. From the WebSphere Administrator, define a WorkManager for use by your application.           From the admin, choose Resources > Asynchronous Beans > Work managers.           By default, the DefaultWorkManager is available at the wm/default jndi-name.         Also, you can add a separate WorkManager for your application.
          6. Deploy the WAR file. During deployment,  map the WorkManager resource-ref to an actual JNDI name for your WorkManager.           For the DefaultWorkManager,         wm/MessagingWorkManager (name used by your web.xml) maps to  wm/default (the JNDI name of the actual server resource).
          7. (Optional) To enable custom authentication, open the WebSphere Administrator and configure a custom user registry using the files under install-root/resources/security/websphere/ as usersFile and groupsFile custom properties.