Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » OSEE » Getting client/server running - worked for me
Getting client/server running - worked for me [message #15304] Mon, 18 May 2009 08:09 Go to next message
Mark D-B is currently offline Mark D-B
Messages: 188
Registered: July 2009
Senior Member
This assumes you have created an empty OSEE PostgreSQL database already
and have downloaded the "all-in-one" package.

Create a connection.xml file (located in C:\Program Files\OSEE\Application
Server in my case) with the following content, where "OSEEServer" is the
DNS/hosts file name for the machine that is going to be running the app
server.

<DbConnection>

<DatabaseInfo id="postgresqlInfo">
<DatabaseHome key="#DBHOME#"/>
<DatabaseName key="#DBNAME#" value="OSEE" />
<DatabaseType key="#TYPE#" value="postgresql" />
<Prefix key="#PREFIX#" value="jdbc:postgresql" />
<UserName key="#USERNAME#" value="osee" />
<Password key="#PASSWORD#" value="osee" />
<Host key="#HOST#" value="@AvailableDbServices.hostAddress" />
<Port key="#PORT#" value="@AvailableDbServices.port" />
</DatabaseInfo>

<ConnectionDescription id="postgresql" >
<Driver>org.postgresql.Driver</Driver>
<Url>#PREFIX#://#HOST#:#PORT#/#DBHOME##DBNAME#</Url>
</ConnectionDescription>

<AvailableDbServices>
<Server id="OSEE" dbInfo="postgresqlInfo"
hostAddress="OSEEServer" port="5432"
connectsWith="postgresql" isProduction="false" />
</AvailableDbServices>
</DbConnection>

Then execute the following command line:

java -Dosee.log.default=INFO -Dorg.osgi.service.http.port=8089
-Dosgi.compatibility.bootdelegation=true -Xmx512m -Dequinox.ds.debug=true
-Dosee.connection.info.uri="C:\Program Files\OSEE\Application
Server\connection.xml" -Dosee.db.connection.id=OSEE -jar
org.eclipse.osgi_3.4.0.v20080326.jar -console

The server is now up and running.

Modify the oseeDbInitRemotec.ini file so it contains:

-startup
plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819. jar
--launcher.library
plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101 .R34x_v20080731
-application
org.eclipse.osee.framework.database.configClient
-showsplash
org.eclipse.osee.framework.ui.product
--launcher.XXMaxPermSize
256m
-console
-debug
-vmargs
-Xms40m
-Xmx700m
-Dosee.choice.on.db.init=OSEE Demo Database
-Dosee.prompt.on.db.init=false
-Dosee.log.default=INFO
-Dosee.application.server=http://OSEEServer:8089
-Dosee.authentication.protocol=trustAll

Execute oseeDbInitRemotec.exe - this will initialise the database.

Modify the oseeAppServerRemotec.ini file so it contains:

-startup
plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819. jar
--launcher.library
plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101 .R34x_v20080731
-product
org.eclipse.osee.framework.ui.product.osee
-showsplash
org.eclipse.osee.framework.ui.product
--launcher.XXMaxPermSize
256m
-console
-vmargs
-Xms40m
-Xmx700m
-Dosee.log.default=INFO
-Dosee.application.server=http://OSEEServer:8089
-Dosee.authentication.protocol=trustAll

Execute oseeAppServerRemotec.exe to run the client.
Re: Getting client/server running - worked for me [message #15437 is a reply to message #15304] Thu, 21 May 2009 17:27 Go to previous messageGo to next message
Ray Joseph is currently offline Ray Joseph
Messages: 87
Registered: July 2009
Member
Mark,

Thank you very much for the effort to post the process. With your help, I
found many holes in my attempts. But I still am not running. I have
tried it on three different machines.

The process hangs after entering the script at the app_server directory.
The transaction looks like:

C:\osee\app_server_0.7.0>java -Dosee.log.default=INFO -Dorg.osgi.service.http.p
rt=8089 -Dosgi.compatibility.bootdelegation=true -Xmx512m
-Dequinox.ds.debug=t
ue -Dosee.connection.info.uri="C:\osee\app_server_0.7.0\connection.xml "
-Dosee.
b.connection.id=OSEE -jar org.eclipse.osgi_3.4.0.v20080326.jar -console

osgi> May 21, 2009 9:58:40 AM org.mortbay.http.HttpServer doStart
INFO: Version Jetty/5.1.x
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started org.mortbay.jetty.servlet.ServletHandler@1394894
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started HttpContext[/,/]
May 21, 2009 9:58:40 AM org.mortbay.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:8089
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started org.mortbay.http.HttpServer@134a7d8
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.internal.UriDbConnect ionInfo
geDbInformation (36)
Loading connection info from: [C:\osee\app_server_0.7.0\connection.xml]

Adding:
org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @6f7d2
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.internal.ServerTaskSc heduler
adServerTask (41)
Adding task: Clean up join tables

Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties
getOseeAppicationServerData (54)
Application Server Data: [C:\Documents and Settings\rjoseph]

Registered servlet '/osee/branch'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/install/info'
Registered servlet '/osee/resource'
Registered servlet '/osee/search'
Registered servlet '/osee/search/tagger'
Registered servlet '/osee/server/lookup'
Registered servlet '/osee/session'
Registered servlet '/osee/client/loopback'
Thu May 21 09:58:43 CDT 2009
org.eclipse.osee.framework.search.engine.intenal.SearchEngin eTagger
INFO org.eclipse.osee.framework.search.engine.internal.StartUpRun nable
run45)
Tagging on Server Startup was not run.

Thu May 21 09:59:00 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStoe
deregisterWithDb (63)
Server lookup table not initialized

Thu May 21 09:59:20 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStoe
registerWithDb (80)
Server lookup table not initialized
_______________

It hangs at this point.

the PG_log has no entries during this time.

It looks like there is a problem registering with the Db. I assume this
is the PostgreSQL. Any suggestions on how to move forward?

Addditionally, I already have SVN and TSVN running on all the machines
that I have tried to run osee. Is there a possibility that there is a
clash here? When I close the command window where the script hangs, the
Windows Task Manager shows that the postgres.exe process runs for a short
duration and then stops. I guess this means that the closure is
interacting with PostgreSQL. The pg log does not show any activity during
the osee process.



Thanks,
Ray
Re: Getting client/server running - worked for me [message #15502 is a reply to message #15437] Mon, 01 June 2009 14:42 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-B
Messages: 188
Registered: July 2009
Senior Member
Hi Ray,

Sorry for the long delay in replying, I've been unable to do much OSEE
stuff for the last couple of weeks due to project demands.

As I recall, that output is okay for having started the app server but not
yet having run the database initialisation. If you run the init, it should
produce more output in the app server window as it creates the tables.
Re: Getting client/server running - worked for me [message #15598 is a reply to message #15502] Mon, 01 June 2009 17:02 Go to previous messageGo to next message
Ray Joseph is currently offline Ray Joseph
Messages: 87
Registered: July 2009
Member
Mark,

Thank you for the comment. I thought the run was not complete as the
activity never completed. It would just hang (I left it as long as a day)
at that point without returning to the osgi> prompt. And there were no
new tables in the db.

But I will move forward with the init.

Ray
Re: Getting client/server running - worked for me [message #15629 is a reply to message #15598] Mon, 01 June 2009 22:40 Go to previous message
Ray Joseph is currently offline Ray Joseph
Messages: 87
Registered: July 2009
Member
I think I've got it.
The application server was launched (java . . . script). It does not
complete, it continues to try to make connections - ignore it and let it
run.

The database was initialized (eclipse . . . script).
THe OSEE client was initialized (eclipse . . . script).

So far, I have taken it to changing to the SAW_Bld_2 branch (p.45/117).

But I did run into what appears to be a problem. While waiting for
completion of "Populate Demo Actions", there was an error (listed below).
Is this error of any concern?

Here is the error report:

OSEE Error
The branch argument can not be null.
Reason:
The branch argument can not be null.

Details>>
The branch argument can not be null
The branch argument can not be null

org.eclipse.osee.framework.skynet.core.artifact.BranchManage r.setDefaultBranch(BranchManager.java:543)

org.eclipse.osee.ats.config.demo.config.DemoDbUtil.setDefaul tBranch(DemoDbUtil.java:62)

org.eclipse.osee.ats.config.demo.config.PopulateDemoActions. makeAction1ReqChanges(PopulateDemoActions.java:213)

org.eclipse.osee.ats.config.demo.config.PopulateDemoActions. run(PopulateDemoActions.java:132)

org.eclipse.osee.ats.config.demo.config.PopulateDemoActions. run(PopulateDemoActions.java:92)

org.eclipse.osee.framework.ui.skynet.widgets.xnavigate.XNavi gateComposite.handleDoubleClick(XNavigateComposite.java:214)

org.eclipse.osee.ats.navigate.AtsNavigateComposite.handleDou bleClick(AtsNavigateComposite.java:92)

org.eclipse.osee.ats.navigate.AtsNavigateComposite.handleDou bleClick(AtsNavigateComposite.java:60)

org.eclipse.osee.framework.ui.skynet.widgets.xnavigate.XNavi gateComposite$3.handleEvent(XNavigateComposite.java:100)
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3823)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3422)
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)

org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)

org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)

org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)

org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)

org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)

org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)

org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)

org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
org.eclipse.equinox.launcher.Main.run(Main.java:1236)

Ray

BTW, where can I learn how to read this type of output?
Re: Getting client/server running - worked for me [message #573942 is a reply to message #15304] Thu, 21 May 2009 17:27 Go to previous message
Ray Joseph is currently offline Ray Joseph
Messages: 87
Registered: July 2009
Member
Mark,

Thank you very much for the effort to post the process. With your help, I
found many holes in my attempts. But I still am not running. I have
tried it on three different machines.

The process hangs after entering the script at the app_server directory.
The transaction looks like:

C:\osee\app_server_0.7.0>java -Dosee.log.default=INFO -Dorg.osgi.service.http.p
rt=8089 -Dosgi.compatibility.bootdelegation=true -Xmx512m
-Dequinox.ds.debug=t
ue -Dosee.connection.info.uri="C:\osee\app_server_0.7.0\connection.xml "
-Dosee.
b.connection.id=OSEE -jar org.eclipse.osgi_3.4.0.v20080326.jar -console

osgi> May 21, 2009 9:58:40 AM org.mortbay.http.HttpServer doStart
INFO: Version Jetty/5.1.x
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started org.mortbay.jetty.servlet.ServletHandler@1394894
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started HttpContext[/,/]
May 21, 2009 9:58:40 AM org.mortbay.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:8089
May 21, 2009 9:58:40 AM org.mortbay.util.Container start
INFO: Started org.mortbay.http.HttpServer@134a7d8
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.internal.UriDbConnect ionInfo
geDbInformation (36)
Loading connection info from: [C:\osee\app_server_0.7.0\connection.xml]

Adding:
org.eclipse.osee.framework.core.server.internal.ServerDataba seProvider @6f7d2
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.internal.ServerTaskSc heduler
adServerTask (41)
Adding task: Clean up join tables

Registered servlet '/GET.ARTIFACT'
Registered servlet '/osee/artifact'
Thu May 21 09:58:40 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO org.eclipse.osee.framework.core.server.OseeServerProperties
getOseeAppicationServerData (54)
Application Server Data: [C:\Documents and Settings\rjoseph]

Registered servlet '/osee/branch'
Registered servlet '/osee/branch/exchange'
Registered servlet '/osee/install/info'
Registered servlet '/osee/resource'
Registered servlet '/osee/search'
Registered servlet '/osee/search/tagger'
Registered servlet '/osee/server/lookup'
Registered servlet '/osee/session'
Registered servlet '/osee/client/loopback'
Thu May 21 09:58:43 CDT 2009
org.eclipse.osee.framework.search.engine.intenal.SearchEngin eTagger
INFO org.eclipse.osee.framework.search.engine.internal.StartUpRun nable
run45)
Tagging on Server Startup was not run.

Thu May 21 09:59:00 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStoe
deregisterWithDb (63)
Server lookup table not initialized

Thu May 21 09:59:20 CDT 2009
org.eclipse.osee.framework.core.server.CoreSeverActivator
INFO
org.eclipse.osee.framework.core.server.internal.ApplicationS erverDataStoe
registerWithDb (80)
Server lookup table not initialized
_______________

It hangs at this point.

the PG_log has no entries during this time.

It looks like there is a problem registering with the Db. I assume this
is the PostgreSQL. Any suggestions on how to move forward?

Addditionally, I already have SVN and TSVN running on all the machines
that I have tried to run osee. Is there a possibility that there is a
clash here? When I close the command window where the script hangs, the
Windows Task Manager shows that the postgres.exe process runs for a short
duration and then stops. I guess this means that the closure is
interacting with PostgreSQL. The pg log does not show any activity during
the osee process.



Thanks,
Ray
Re: Getting client/server running - worked for me [message #573990 is a reply to message #15437] Mon, 01 June 2009 14:42 Go to previous message
Mark D-B is currently offline Mark D-B
Messages: 188
Registered: July 2009
Senior Member
Hi Ray,

Sorry for the long delay in replying, I've been unable to do much OSEE
stuff for the last couple of weeks due to project demands.

As I recall, that output is okay for having started the app server but not
yet having run the database initialisation. If you run the init, it should
produce more output in the app server window as it creates the tables.
Re: Getting client/server running - worked for me [message #574056 is a reply to message #15502] Mon, 01 June 2009 17:02 Go to previous message
Ray Joseph is currently offline Ray Joseph
Messages: 87
Registered: July 2009
Member
Mark,

Thank you for the comment. I thought the run was not complete as the
activity never completed. It would just hang (I left it as long as a day)
at that point without returning to the osgi> prompt. And there were no
new tables in the db.

But I will move forward with the init.

Ray
Re: Getting client/server running - worked for me [message #574081 is a reply to message #15598] Mon, 01 June 2009 22:40 Go to previous message
Ray Joseph is currently offline Ray Joseph
Messages: 87
Registered: July 2009
Member
I think I've got it.
The application server was launched (java . . . script). It does not
complete, it continues to try to make connections - ignore it and let it
run.

The database was initialized (eclipse . . . script).
THe OSEE client was initialized (eclipse . . . script).

So far, I have taken it to changing to the SAW_Bld_2 branch (p.45/117).

But I did run into what appears to be a problem. While waiting for
completion of "Populate Demo Actions", there was an error (listed below).
Is this error of any concern?

Here is the error report:

OSEE Error
The branch argument can not be null.
Reason:
The branch argument can not be null.

Details>>
The branch argument can not be null
The branch argument can not be null

org.eclipse.osee.framework.skynet.core.artifact.BranchManage r.setDefaultBranch(BranchManager.java:543)

org.eclipse.osee.ats.config.demo.config.DemoDbUtil.setDefaul tBranch(DemoDbUtil.java:62)

org.eclipse.osee.ats.config.demo.config.PopulateDemoActions. makeAction1ReqChanges(PopulateDemoActions.java:213)

org.eclipse.osee.ats.config.demo.config.PopulateDemoActions. run(PopulateDemoActions.java:132)

org.eclipse.osee.ats.config.demo.config.PopulateDemoActions. run(PopulateDemoActions.java:92)

org.eclipse.osee.framework.ui.skynet.widgets.xnavigate.XNavi gateComposite.handleDoubleClick(XNavigateComposite.java:214)

org.eclipse.osee.ats.navigate.AtsNavigateComposite.handleDou bleClick(AtsNavigateComposite.java:92)

org.eclipse.osee.ats.navigate.AtsNavigateComposite.handleDou bleClick(AtsNavigateComposite.java:60)

org.eclipse.osee.framework.ui.skynet.widgets.xnavigate.XNavi gateComposite$3.handleEvent(XNavigateComposite.java:100)
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3823)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3422)
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)

org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)

org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)

org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)

org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)

org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)

org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)

org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)

org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
org.eclipse.equinox.launcher.Main.run(Main.java:1236)

Ray

BTW, where can I learn how to read this type of output?
Previous Topic:Running the app_server
Next Topic:No changes without an Action
Goto Forum:
  


Current Time: Wed Jul 30 11:35:56 EDT 2014

Powered by FUDForum. Page generated in 0.02438 seconds