Skip navigation
Currently Being Moderated

Deploying sample applications in mosaic

Dec 16, 2009 11:56 AM

Hello, i want to deploy the applications in Mosaic. I'm following these instructions:

 

Use the Ant build files provided with the Mosaic ES2 installation to deploy sample applications to the server.

To run Ant, type ant from the command line. When you do not provide arguments, Ant looks for a build.xml file in the current directory.

For descriptions of the sample applications, see Sample applications.

#

Deploy all samples and demos

In the following directory, run Ant:

  • [Mosaic ES2 install directory]/samples/

#

Deploy the general sample applications

In the following directory, run Ant:

  • [Mosaic ES2 install directory]/samples/general/

#

Deploy the MAX2009 application

In the following directory, run Ant:

  • [Mosaic ES2 install directory]/samples/max2009/

 

 

I've set the ant_home enviromment variable but it still gives me the 'ant' is not recognized as an internal or external command,
operable program or batch file.

 

Thanks.

 
Replies
  • Currently Being Moderated
    Dec 16, 2009 1:05 PM   in reply to Mário Figueira

    Usually this is because the build.xml file is not able to point to the mosaicTasks.jar.

     

    For example:

    <project name="LiveCycle Mosaic MySamples" default="deploy">
        <taskdef resource="mosaic.tasks" classpath="../bin/mosaicTasks.jar" />

    ....

     

     

     

    If the classpath statement in the second line can't find the jar file then it will fail.  The jar file is used to upload catalogs and applications to the mosaic server

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 17, 2009 7:36 AM   in reply to Mário Figueira

    humm, interesting.  WebSphere is obviously blocking the file upload.

     

    Are there other LiveCycle products deployed to that WebSphere instance?

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 17, 2009 8:24 AM   in reply to Mário Figueira

    Okay, that's good.  It means that the LiveCycle UserManager and Repository components are deployed.

     

    The other thing I would check is the username and password sections of the build.xml file.  They will need to be set to a user that has the ROLE_MOSAIC_DESIGNER role in Mosaic.  By default there should be a user called designer with a password of password that has that role.

     

    ....

    <mosaic-catalog action="import"
                            name="FADesktop_catalog"
                            file="FADesktop_catalog.zip"
                            property="response"
                            server="${server}"
                            port="${port}"
                           username="designer"
                            password="password"
    />
            <echo message="${response}" />
        </target>

     

    ....

     

    <mosaic-application action="import"
                                name="FADesktop"
                                file="applications/FADesktop.xml"
                                property="response"
                                server="${server}"
                                port="${port}"
                               username="designer"
                                password="password"
    />
            <echo message="${response}" />

    ....

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 18, 2009 5:25 AM   in reply to Mário Figueira

    Darn, well so much for the easy stuff.

     

    There is another spot where the security may have gotten screwed up, but by default this should be okay.  In the mosaic.war file that you deployed to WebSphere is a security.xml file.  (You can open the war file using a zip program.)  the file is located in the WEB-INF directory.

     

    This file is where the roles are set for each user (like "designer").  Look for a tag marked security:authentication-provider.  Make sure the "designer" user has the ROLE_MOSAIC_DESIGNER role.  Should look something like:

     

    <security:authentication-provider>
            <security:user-service>
                <security:user name="user" password="password" authorities="ROLE_MOSAIC_END_USER"/>
                <security:user name="designer" password="password" authorities="ROLE_MOSAIC_END_USER, ROLE_MOSAIC_DESIGNER"/>
            </security:user-service>
        </security:authentication-provider>

     

    If that is set properly then I can only imagine that its something on the IBM side.  Perhaps additional security has been attached to the mosaic application when the WAR file was deployed.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2010 12:45 AM   in reply to Hodmi

    I have the exact same error with JBoss turnkey LC ES2. I've checked the items in the thread and installed according to the instructions to the letter. What likely causes this?

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points