Re: Jetspeed2 Installation

David Encinas Fri, 08 May 2009 11:44:21 -0700

Hi,

I (completly new to this) was able to build v2.1.3 using maven and, deploy to tomcat and connecto to mysql.

I followed steps in

http://portals.apache.org/jetspeed-2.1.3/tutorials/stepbystep/guide-building-custom-portal-maven2.html

and changed 2.1-dev to 2.1.3 in the mvn command:

mvn archetype:create 
    -DarchetypeGroupId=org.apache.portals.jetspeed-2 
    -DarchetypeArtifactId=portal-archetype -DarchetypeVersion=2.1.3
    -DgroupId=bluesunrise 
    -DartifactId=jetexpress-2 
    -Dversion=1.0

Then it took my some time to configure the settings.xml. But now it is working. I attach it just in case:

<?xml version="1.0" encoding="UTF-8"?>
<!--
The Maven 2 profile is one place to set user or project specific settings.


This settings file is useful for building the Apache Portals Jetspeed from the 
subversion codebase. It is also useful for choosing a custom database to use 
with Jetspeed. The default database is Apache DB Derby database.

You will need to provide your own value anywhere you see the text SET*.

This file is placed in ~/.m2 by convention. User defined profiles must be 
defined or extended with these settings to perform a complete J2 build and 
deployment. -->
<settings xmlns="http://maven.apache.org/POM/4.0.0";>

    <!-- Local Repository Location -->

	<localRepository>/Users/david/dev/maven/repository/</localRepository>

    <!-- http://people.apache.org/~ate/jetspeed-2.2-maven-plugins/index.html -->
    	<pluginGroups>
    		<pluginGroup>org.apache.portals.jetspeed-2</pluginGroup>
        	<pluginGroup>org.apache.pluto</pluginGroup> 
    	</pluginGroups>

    <!-- Jetspeed-2 Profiles -->

    <profiles>

        <!-- Jetspeed Settings Profile -->
        <profile>
            <id>jetspeed-settings</id>
            <activation>
                <activeByDefault>true</activeByDefault>
            </activation>
            <properties>

                <!-- Build profiles configuration -->
                	<org.apache.jetspeed.env.deploy.target>tomcat</org.apache.jetspeed.env.deploy.target>
                	<org.apache.jetspeed.env.deploy.type>full</org.apache.jetspeed.env.deploy.type>
                	<org.apache.jetspeed.env.deploy.db.psml>false</org.apache.jetspeed.env.deploy.db.psml>

                <!-- Jetspeed-2 deployment properties -->

                	<org.apache.jetspeed.server.home>/Users/david/dev/tomcat/</org.apache.jetspeed.server.home>
                	<org.apache.jetspeed.catalina.version.major>5.5</org.apache.jetspeed.catalina.version.major>
                	<org.apache.jetspeed.services.autodeployment.server>localhost</org.apache.jetspeed.services.autodeployment.server>
                	<org.apache.jetspeed.services.autodeployment.port>8080</org.apache.jetspeed.services.autodeployment.port>
                <!-- tomcat-users.xml must include a user with the manager role -->
                	<org.apache.jetspeed.services.autodeployment.user>XXXXX</org.apache.jetspeed.services.autodeployment.user>
                	<org.apache.jetspeed.services.autodeployment.password>XXXXX</org.apache.jetspeed.services.autodeployment.password>
    
            </properties>
        </profile>

        <!-- The appropriate database profile may already be defined here. Please verify the settings 

           Each database platform defines two schema. One for testing and one for production.
           You will need to copy your driver jar(s) to the ${org.apache.jetspeed.server.home}/shared/lib
           directory and define the name, url, driver, username, and password for testing and production. -->

        <!-- Jetspeed Derby Embedded Profile (see activeProfiles) -->
        <profile>
            <id>jetspeed-derby-embedded</id>
            <activation>
                <activeByDefault>false</activeByDefault>
            </activation>
            <properties>
                <!-- Derby embedded database properties -->
                	<org.apache.jetspeed.test.jdbc.drivers.path>${org.apache.jetspeed.server.home}/shared/lib/derby-10.2.1.6.jar</org.apache.jetspeed.test.jdbc.drivers.path>
                	<org.apache.jetspeed.test.database.default.name>derby</org.apache.jetspeed.test.database.default.name>
                	<org.apache.jetspeed.test.database.url>jdbc:derby:/tmp/j2test;create=true</org.apache.jetspeed.test.database.url>
                	<org.apache.jetspeed.test.database.driver>org.apache.derby.jdbc.EmbeddedDriver</org.apache.jetspeed.test.database.driver>
                	<org.apache.jetspeed.test.database.user></org.apache.jetspeed.test.database.user>
                	<org.apache.jetspeed.test.database.password>SETPASSWORD</org.apache.jetspeed.test.database.password>
                	<org.apache.jetspeed.production.jdbc.drivers.path>${org.apache.jetspeed.server.home}/shared/lib/derby-10.2.1.6.jar</org.apache.jetspeed.production.jdbc.drivers.path>
                	<org.apache.jetspeed.production.database.default.name>derby</org.apache.jetspeed.production.database.default.name>
                	<org.apache.jetspeed.production.database.url>jdbc:derby:/tmp/j2;create=true</org.apache.jetspeed.production.database.url>
                	<org.apache.jetspeed.production.database.driver>org.apache.derby.jdbc.EmbeddedDriver</org.apache.jetspeed.production.database.driver>
                	<org.apache.jetspeed.production.database.user></org.apache.jetspeed.production.database.user>
                	<org.apache.jetspeed.production.database.password>SETPASSWORD</org.apache.jetspeed.production.database.password>
            </properties>
        </profile>

        <!-- Jetspeed MySQL Profile -->
        <profile>
            <id>jetspeed-mysql</id>
            <activation>
                <activeByDefault>false</activeByDefault>
            </activation>
            <properties>
                <!-- MySQL database properties -->
                <org.apache.jetspeed.test.jdbc.drivers.path>${org.apache.jetspeed.server.home}/shared/lib/mysql-connector-java-5.1.7-bin.jar</org.apache.jetspeed.test.jdbc.drivers.path>
                <org.apache.jetspeed.test.database.default.name>mysql</org.apache.jetspeed.test.database.default.name>
                <org.apache.jetspeed.test.database.url>jdbc:mysql://localhost/j2test</org.apache.jetspeed.test.database.url>
                <org.apache.jetspeed.test.database.driver>com.mysql.jdbc.Driver</org.apache.jetspeed.test.database.driver>
                <org.apache.jetspeed.test.database.user>XXXXX</org.apache.jetspeed.test.database.user>
                <org.apache.jetspeed.test.database.password>XXXXX</org.apache.jetspeed.test.database.password>
                <org.apache.jetspeed.production.jdbc.drivers.path>${org.apache.jetspeed.server.home}/shared/lib/mysql-connector-java-5.1.7-bin.jar</org.apache.jetspeed.production.jdbc.drivers.path>
                <org.apache.jetspeed.production.database.default.name>mysql</org.apache.jetspeed.production.database.default.name>
                <org.apache.jetspeed.production.database.url>jdbc:mysql://localhost/j2</org.apache.jetspeed.production.database.url>
                <org.apache.jetspeed.production.database.driver>com.mysql.jdbc.Driver</org.apache.jetspeed.production.database.driver>
                <org.apache.jetspeed.production.database.user>XXXXX</org.apache.jetspeed.production.database.user>
                <org.apache.jetspeed.production.database.password>XXXXX</org.apache.jetspeed.production.database.password>
            </properties>
        </profile>
    </profiles>

    <activeProfiles>

        <!-- Apache DB Derby Embedded is the default Jetspeed database -->
        <!--
        <activeProfile>jetspeed-derby-embedded</activeProfile>
        <activeProfile>jetspeed-db-embedded-derby</activeProfile>-->

        <!-- MySQL database -->
        <!--Uncomment this if you are using the MySQL database-->
        <activeProfile>jetspeed-mysql</activeProfile>

    
        <!-- Drivers path configured database profile -->
        <!-- <activeProfile>jetspeed-db-drivers-path</activeProfile> -->
    </activeProfiles>
</settings>

The only problem I am having now is that with mvn tomcat,min , the installation has no user so I do not know how to login to the app :)

Hope this help.

Regards,

David.

On May 8, 2009, at 5:27 PM, Ron Wheeler wrote:

The user community is trying to fix up the documentation but we are very early into the process.

There is a wiki where we are trying to get an outline of what we all would have liked to have when we started.
http://wiki.apache.org/portals/Jetspeed2
It is an old unused wiki and I have started to clean out some of the old stuff.
I have asked Hippo(Jetspeed developers) to update the roadmap on the wiki.

If you have some suggestions about what you think we should create, please let the group know.

I have some ideas about how the documentation should be organized to allow different types of users to get the information that they need.
A person who is trying to run jetspeed "out of the box" with no customization(evaluator for example) needs different information than a developer who needs to modify the way that users login which is different from the info required by someone who is going to build custom portlets

I would like some discussion about this approach to see if we can build a modular documentation set that will give us as much of a custom view of the documentation as possible while minimizing the number of overlapping documents.

We also need some high level documentation that can help evaluators to understand what they are getting with Jetspeed, the underlying architecture and when this the right way to go.

Ron
Stefano Bianchi wrote:
Hi all,
fine to hear you made it (at least start it), as I tried unsuccesfully to do the same... no way to make it work on MySQL backend.
I used J1.X for several projects, but the time I am spending to evaluate J2 is definitively too high...
My sincere congratulations to the developer team, nevertheless consider it might be hard for "dummy" interested parties to start using J2.
My two cents, just a comment.
Be well,
Stefano

----- Original Message ----- From: "rache" <rachehernan...@yahoo.com>
To: <jetspeed-user@portals.apache.org>
Sent: Friday, May 08, 2009 10:55 AM
Subject: Jetspeed2 Installation

Hi,

I'm new to portals and I was able to install Jetspeed2 using the demo
installer jar.
I used Oracle XE as the database. The portal was fine except for some
portlets that are not working.

I have a couple of questions though.
I wanted to create my own portal following the JetExpress tutorial.
However, even if I use a different database for the 2nd portal i get an
exception
on my container name not being unique; jetspeed - actionvalve bean can't be
created due to this.
Even if I changed the name in the mvn command to use jetexpress, I wonder
why its throwing this.

So I just installed a fresh Tomcat instance and used mysql as the 2nd
database.
Custom portal was deployed but I can't login using any of the credentials
that comes along.
Its sayign that the DefaultLoginModule class can not be found.

I checked the tomcat lib folder and it has the security jar.

Any help will be greatly appreciated.

Thanks,
Rache
--
View this message in context: http://www.nabble.com/Jetspeed2-Installation-tp23442409p23442409.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org

Re: Jetspeed2 Installation

Reply via email to