Home » Eclipse Projects » OSEE » Install problems
| Install problems [message #12601] |
Sat, 18 April 2009 02:53  |
 Rob
Messages: 8
Registered: July 2009 |
Junior Member |
|
|
I am looking for a requirements management/ configuration management tools
and osee seemed to be just the sort of thing I was looking for.
I am relatively new to the eclipse world and can't seem to get osee
running.
I am using Windows XP.
I have downloaded postgresql and installed successfully.
I added the osee user and created the database as per these instructions:
http://www.eclipse.org/osee/documentation/installation/postg resql_install.php
I have downloaded eclipse, and it starts fine.
I have downloaded OSEE 0.7.0 Integration build and installed the
dependencies listed here:
http://www.eclipse.org/osee/documentation/installation/requi rements.php
When I try to initialize the database with the DbInit application as
indicated here
http://www.eclipse.org/osee/documentation/installation/db_in it.php
I get a Runtime error that DbInit is not found. The log file is below.
Can anyone help me?
Thanks in advance.
!SESSION 2009-04-17 20:12:54.250
-----------------------------------------------
eclipse.buildId=M20090211-1700
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -application
org.eclipse.osee.framework.application.server.DbInit
Command-line arguments: -os win32 -ws win32 -arch x86 -application
org.eclipse.osee.framework.application.server.DbInit -console
!ENTRY org.eclipse.osgi 4 0 2009-04-17 20:12:59.390
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application
"org.eclipse.osee.framework.application.server.DbInit" could not be found
in the registry. The applications available are:
org.eclipse.ant.core.antRunner, org.eclipse.equinox.app.error,
org.eclipse.equinox.p2.artifact.repository.mirrorApplication ,
org.eclipse.equinox.p2.director.app.application,
org.eclipse.equinox.p2.metadata.generator.EclipseGenerator,
org.eclipse.equinox.p2.metadata.repository.mirrorApplication ,
org.eclipse.equinox.p2.reconciler.application,
org.eclipse.help.base.infocenterApplication,
org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool,
org.eclipse.ui.ide.workbench, org.eclipse.update.core.standaloneUpdate,
org.eclipse.update.core.siteOptimizer, org.eclipse.ant.ui.antRunner,
org.eclipse.birt.report.debug.core.ReportDebugger,
org.eclipse.birt.report.engine.ReportExecutor,
org.eclipse.datatools.connectivity.console.profile.StorageFi leEditor,
org.eclipse.emf.codegen.CodeGen, org.eclipse.emf.codegen.JMerger,
org.eclipse.emf.codegen.ecore.Generator,
org.eclipse.emf.importer.ecore.Ecore2GenModel,
org.eclipse.emf.importer.java.Java2GenModel,
org.eclipse.emf.importer.rose.Rose2GenModel,
org.eclipse.jdt.apt.core.aptBuild, org.eclipse.jdt.core.JavaCodeFormatter,
org.eclipse.pde.build.Build,
org.eclipse.pde.junit.runtime.uitestapplication,
org.eclipse.pde.junit.runtime.legacytestapplication,
org.eclipse.pde.junit.runtime.coretestapplication,
org.eclipse.pde.junit.runtime.coretestapplicationnonmain,
org.eclipse.wst.jsdt.core.JavaCodeFormatter,
org.eclipse.wst.server.preview.preview,
org.eclipse.osee.framework.database.configClient,
org.eclipse.osee.framework.database.availableDbTasks,
org.eclipse.osee.framework.jini.JiniLookup,
org.eclipse.osee.framework.messaging.event.skynet.EventServi ce.
at
org.eclipse.equinox.internal.app.EclipseAppContainer.startDe faultApp(EclipseAppContainer.java:242)
at
org.eclipse.equinox.internal.app.MainApplicationLauncher.run (MainApplicationLauncher.java:29)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
|
|
| | | | | | | | | | | |
| Re: Install problems [message #13646 is a reply to message #13557] |
Fri, 24 April 2009 20:42  |
Venkat Mantripragada
Messages: 8
Registered: July 2009 |
Junior Member |
|
|
Venkat Mantripragada wrote:
> I don't think not executing oseePostgresMicroc.exe will stop us from
> initializing our own database , according to my understanding all it does
> is pre-initialize database by connecting to external server (May be the
> university example Don explained in his screen cast)...what you can do in
> documentation (http://osee.microdoc.com/node/2) for OSEE client launch
> options follow step 2 "Local Application Server with Local PostgreSql
> Database" instead of step 1 "Pre-initialized Database".
> Anyways i was also looking at oseePostgresMicro configuration settings and
> i thought there could be two possibilities why this error is occuring:
> 1) There is "http://osee.microdoc.com:8089/" parameter passed to
> application server. I am more thinking there is something wrong there, may
> be they(developers) removed data from the 8089 port. In the installation
> documentation, they say
> "Launch the OSEE Eclipse client using <install dir>oseePostgresMicroc.exe
> to connect to the Microdoc repository. You must have access to port 5432
> to be able to connect"
> So i am guessing if we change the port number from 8089 to 5432 in
> configuration settings it should work...
> 2) In the version 0.7.0 the
> "org.eclipse.osee.framework.application.server.DbInit" is not registering
> (or) doesn't exist. I am not sure where this file should be, i have
> checked appserver plugins and it doesn't exist there and i think it should
> be replaced with "org.eclipse.osee.demo.db.connection_0.4.0.200902191228"
> or something else
> Anyways i would try the case 1 by myself soon and can tell you what
> happened...
> I just thought of sharing this...
> I would really appreciate if developers can answer this connection to
> pre-initialized database problem. Also in the documentation
> (http://osee.microdoc.com/node/2) you have indicated run populate demo
> action, but i am missing it, can you provide me some detail guidance where
> that demo action is?
There you go, if you replace the db_init with the below statement, it
works, I have successfully populate my OSEE 0.7 with the john hopkins demo
data...
eclipsec -application org.eclipse.osee.framework.database.configClient
-vmargs -Xmx256m -Dosee.log.default=INFO
-Dosee.application.server=http://localhost:8089
-Dosee.authentication.protocol=trustAll -Dosee.prompt.on.db.init=false
-Dosee.choice.on.db.init="OSEE Demo Database"
|
|
| |
| Re: Install problems [message #13750 is a reply to message #13518] |
Tue, 28 April 2009 21:11 |
Venkat Mantripragada
Messages: 8
Registered: July 2009 |
Junior Member |
|
|
Trent Johnson wrote:
> Rob wrote:
> ...
>> Install postgresql as per the instructions.
>> Run the the osee server (i.e. the runServer-PgSqlLocalAll.sh)
>> run oseeDbInitLocalc.exe
>> run oseeLocalc.exe
> ...
> I agree that these steps will provide a running eclipse instance with
> which you can learn the osee capabilities and actions available.
> However it doesn't get me a clean initialized database that I can use for
> my own purposes using my own installation of eclipse/plugins/and tools.
> I am still wondering what could cause the problem documented in the first
> message of this thread, i.e. the failure of the documented DbInit step
> located at
> " http://www.eclipse.org/osee/documentation/installation/db_in it.php"
> (which I see is now retired).
> Comments anyone?
> Trent
***************************-------************************** *****
Sorry i got this wrong , Trent is right. We cannot get a clean database by
following any of steps in microdoc or in the retired link. when we execute
statement specified in
http://www.eclipse.org/osee/documentation/installation/db_in it.php i get
the following error:
************************************************************ ***********
!SESSION 2009-04-28 14:49:34.705
-----------------------------------------------
eclipse.buildId=M20080911-1700
java.version=1.6.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -application
org.eclipse.osee.framework.application.server.DbInit
Command-line arguments: -os win32 -ws win32 -arch x86 -application
org.eclipse.osee.framework.application.server.DbInit -console
!ENTRY org.eclipse.osgi 4 0 2009-04-28 14:49:38.096
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application
"org.eclipse.osee.framework.application.server.DbInit" could not be found
in the registry.
************************************************************ ******************
The only way to solve the problem is getting the file through Update
manager in eclipse, then only eclipse will register. But, where is the
file? which one should i update to get this file?
If anybody knows the solution, please provide it. An updated documentation
is greatly appreciated.
Please note: The documentation for running a demo database, screen casts,
wiki is very good, i got understanding of the tool by using demo data. But
when i want to start piloting this good tool in our company, there is no
clear documentation on where to start for a clean installation.
Thank you.
|
|
| | | | | | |
| Re: Install problems [message #572830 is a reply to message #12779] |
Tue, 21 April 2009 15:02 |
Ryan D. Brooks
Messages: 100
Registered: July 2009 |
Senior Member |
|
|
Rob,
The quick answer is that the messages you see indicate that the server
started correctly.
The first word in the log messages indicates the severity (i.e. INFO).
The messages you are noticing about Tagging and Server lookup table not
initialized are of type INFO and do not represent a problem. The several
lines such that start with "Registered servlet" indicate the successful
start-up of various OSEE services.
The server is up and running and the next step is to initialize the
database. The message about the Server lookup table not initialized is
due to the database tables not yet existing (they are created during the
database initialization).
I see there is another post about the database initialization, so I will
reply to that one with more information.
Thanks,
Ryan
Thanks,
Ryan Brooks
|
|
| | | | |
| Re: Install problems [message #573080 is a reply to message #13557] |
Fri, 24 April 2009 20:42 |
Venkat Mantripragada
Messages: 8
Registered: July 2009 |
Junior Member |
|
|
Venkat Mantripragada wrote:
> I don't think not executing oseePostgresMicroc.exe will stop us from
> initializing our own database , according to my understanding all it does
> is pre-initialize database by connecting to external server (May be the
> university example Don explained in his screen cast)...what you can do in
> documentation (http://osee.microdoc.com/node/2) for OSEE client launch
> options follow step 2 "Local Application Server with Local PostgreSql
> Database" instead of step 1 "Pre-initialized Database".
> Anyways i was also looking at oseePostgresMicro configuration settings and
> i thought there could be two possibilities why this error is occuring:
> 1) There is "http://osee.microdoc.com:8089/" parameter passed to
> application server. I am more thinking there is something wrong there, may
> be they(developers) removed data from the 8089 port. In the installation
> documentation, they say
> "Launch the OSEE Eclipse client using <install dir>oseePostgresMicroc.exe
> to connect to the Microdoc repository. You must have access to port 5432
> to be able to connect"
> So i am guessing if we change the port number from 8089 to 5432 in
> configuration settings it should work...
> 2) In the version 0.7.0 the
> "org.eclipse.osee.framework.application.server.DbInit" is not registering
> (or) doesn't exist. I am not sure where this file should be, i have
> checked appserver plugins and it doesn't exist there and i think it should
> be replaced with "org.eclipse.osee.demo.db.connection_0.4.0.200902191228"
> or something else
> Anyways i would try the case 1 by myself soon and can tell you what
> happened...
> I just thought of sharing this...
> I would really appreciate if developers can answer this connection to
> pre-initialized database problem. Also in the documentation
> (http://osee.microdoc.com/node/2) you have indicated run populate demo
> action, but i am missing it, can you provide me some detail guidance where
> that demo action is?
There you go, if you replace the db_init with the below statement, it
works, I have successfully populate my OSEE 0.7 with the john hopkins demo
data...
eclipsec -application org.eclipse.osee.framework.database.configClient
-vmargs -Xmx256m -Dosee.log.default=INFO
-Dosee.application.server=http://localhost:8089
-Dosee.authentication.protocol=trustAll -Dosee.prompt.on.db.init=false
-Dosee.choice.on.db.init="OSEE Demo Database"
|
|
| |
| Re: Install problems [message #573187 is a reply to message #13518] |
Tue, 28 April 2009 21:11 |
Venkat Mantripragada
Messages: 8
Registered: July 2009 |
Junior Member |
|
|
Trent Johnson wrote:
> Rob wrote:
> ...
>> Install postgresql as per the instructions.
>> Run the the osee server (i.e. the runServer-PgSqlLocalAll.sh)
>> run oseeDbInitLocalc.exe
>> run oseeLocalc.exe
> ...
> I agree that these steps will provide a running eclipse instance with
> which you can learn the osee capabilities and actions available.
> However it doesn't get me a clean initialized database that I can use for
> my own purposes using my own installation of eclipse/plugins/and tools.
> I am still wondering what could cause the problem documented in the first
> message of this thread, i.e. the failure of the documented DbInit step
> located at
> " http://www.eclipse.org/osee/documentation/installation/db_in it.php"
> (which I see is now retired).
> Comments anyone?
> Trent
***************************-------************************** *****
Sorry i got this wrong , Trent is right. We cannot get a clean database by
following any of steps in microdoc or in the retired link. when we execute
statement specified in
http://www.eclipse.org/osee/documentation/installation/db_in it.php i get
the following error:
************************************************************ ***********
!SESSION 2009-04-28 14:49:34.705
-----------------------------------------------
eclipse.buildId=M20080911-1700
java.version=1.6.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -application
org.eclipse.osee.framework.application.server.DbInit
Command-line arguments: -os win32 -ws win32 -arch x86 -application
org.eclipse.osee.framework.application.server.DbInit -console
!ENTRY org.eclipse.osgi 4 0 2009-04-28 14:49:38.096
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application
"org.eclipse.osee.framework.application.server.DbInit" could not be found
in the registry.
************************************************************ ******************
The only way to solve the problem is getting the file through Update
manager in eclipse, then only eclipse will register. But, where is the
file? which one should i update to get this file?
If anybody knows the solution, please provide it. An updated documentation
is greatly appreciated.
Please note: The documentation for running a demo database, screen casts,
wiki is very good, i got understanding of the tool by using demo data. But
when i want to start piloting this good tool in our company, there is no
clear documentation on where to start for a clean installation.
Thank you.
|
|
|
Goto Forum:
Current Time: Wed Jun 07 23:44:43 GMT 2023
Powered by FUDForum. Page generated in 0.03237 seconds |
] 
Search
Help
Register
Login
Home
