There are two kinds of Jetspeed installers. Neither one is dependent on the other. The demo is best for seeing more features. The minimal installer could be useful for basing your own portal distribution upon, or just seeing the basic feature set of Jetspeed.
To run the standard (minimal) installer:
java -jar jetspeed-2.1.4-installer.jar
To run the Jetspeed Demo installer:
java -jar jetspeed-2.1.4-demo-installer.jar
The installers are capable of running on headless (i.e. no gui) machines, and will detect so automatically.
To force the installer in text mode manually, pass in the text parameter:
java -jar jetspeed-2.1.4-installer.jar text
After starting the installer and advancing through the splash and license pages, select the
Install Jetspeed Portal installer operation and continue. The installer will then
prompt for information required for the installation process. Documentation for the other
installer operations used primarily for ETL migration can be found here: ETL Migration Guide.
The installer will ask you to choose a database for storing the Jetspeed database. We provide a default Derby database for demo systems. The Derby database runs in embedded mode inside the Jetspeed/Tomcat JVM. All other databases require additional configuration. If you selected Derby, you can go with the default parameters provided. For all other databases you must first create an area to hold the Jetspeed tables. For some databases this area is called a catalog, others call it a schema, while others call it a database. Consult your database documentation for details on how to create a catalog or schema to hold the Jetspeed tables. Additionally, you may need to create a database user to access the Jetspeed tables. Often it is required to grant access to the schemas (catalogs) for the given user.
Jetspeed supported database list:
If you choose the manual database setup, then the database scripts will not be run and you will need to configure the database manually after the installation. All database scripts are provided in the installation under the database directory. For your specific database, look for the corresponding directory name. During installation, you will be prompted for the following fields after chosing your database types (except for Derby):
Once you have entered all of your parameters, the installer will test the database connection before proceeding. If the connection fails, please go back to the connection configuration setup and provide the correct parameters. If you choose to continue, the database scripts will not be run and you will need to configure the database manually after the installation. Once the installer verifies the database connection, you are ready to proceed with installation process.
Please take note of the location where you are installing on your file system.
Also, on a Windows platform make sure to use a location path without spaces, e.g. NOT under C:\Program Files.
Once you have completed a successful install, you are ready to start the Jetspeed Portal. On linux, here is an example where you have installed to the default location:
cd ~/jetspeed-2.1.4/bin ./startup.sh
On windows, here is an example where you have installed to the default location:
cd C:\Apache\Jetspeed-2.1.4\bin startup.bat
The very first invocation of the portal requires anywhere from 10 seconds to 30 seconds for initial startup and final installation. After starting the server, start up a web browser and navigate to http://localhost:8080/jetspeed/portal
All preconfigured users have the same password as username (for example the admin user has the password admin) If you installed with the Minimal installer, two test accounts are available:
admin -- System administrator, super user devmgr -- Delegated security manager, can manage users with the "dev" (developer) role
If you installed with the Demo installer, several additional test accounts are available:
admin -- System administrator, super user manager - Has system administration rights, but not super user user -- A sample user demonstrating with with a home page and advanced profiled menus tomcat -- A sample user demonstrating a user without a home page jetspeed -- A sample user demonstrating discovery of pages by both group and role fallback profiling algorithms subsite -- Example of how to setup users with a primary subsite role fallback profiling rules subsite2 -- Example of how to setup users with a secondary subsite role fallback profiling rules devmgr -- Delegated security manager, can manage users with the "dev" (developer) role
The Jetspeed Desktop is a client-side JSR-168 aggregation engine. To accesss the Desktop, navigate your browser to http://localhost:8080/jetspeed/desktop When switching between the /desktop and the /portal URLs, logout to start a new session.
After running the installation, you can manually reinitialize the database or even switch to another database. To do so, we provide an Ant script found under the database directory of your installed Jetspeed portal. The database configuration is defined in the database.properties file. To reinitialize or change the database, go to the database directory and edit the database.properties file, save it, and then run ant.
Here is a sample database configuration file:
; Jetspeed Enterprise Portal 2.1 Database setup configuration ; db.type supported values: db2, derby, mssql, mysql, oracle, postgres, sapdb db.type=mysql : for db.type other than derby, the properties below need to be specified db.username=j2 db.password=abracadabra jdbc.url=jdbc:mysql://localhost:3306/prod-2 jdbc.driver.class=com.mysql.jdbc.Driver
If you are configuring a database for the first time after choosing Manual database setup in the installer, or want to try out
a different type of database, make sure to copy the specific JDBC driver for the database to the Tomcat shared/lib folder before running ant.
Note: for Derby, the needed driver is already placed there or available from the database/lib directory of your installed Jetspeed portal.