Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] Re: Web-Admin Deployment Issues

Subject: perfsonar development work

List archive

Re: [pS-dev] Re: Web-Admin Deployment Issues


Chronological Thread 
  • From: "Michael Bischoff" <>
  • To: "Prodromos Gerakios" <>
  • Cc: " developers" <>, "Nicolas Simar" <>
  • Subject: Re: [pS-dev] Re: Web-Admin Deployment Issues
  • Date: Tue, 9 Dec 2008 10:37:57 +0100 (CET)
  • Importance: Normal

> Prodromos Gerakios wrote:
>
>>
>> Hi all,
>>
>>
>> A long time ago we decided that WA should automatically check and
>> modify eXist's default port. In particular it requires *read/write
>> permissions* to the
>> following file:
>>
>> $CATALINA_HOME/webapps/exist/WEB-INF/client.properties
>>
>>
>> Mario and Fausto recently discovered a WA bug in XML-LS and RRDMA
>> services. This is not a WA bug but a deployment issue. In particular, the
>> deployment should
>> ensure that WA was read/write permission to the client.properties file. I
>> hope this helps.
>>
>>
>> Kind regards,
>> Prodromos.
>>
>>
> There is also one additional deployment bug and this certainly holds for
> RRDMA and possibly for XML-LS: The service expects (*initially*) exists
> to be running on 8180 when the default port of eXist (after deployment) is
> 8080. WA
> automatically changes the eXist port (please read above) *but* the first
> time when eXist is
> loaded on the wrong port so the user needs to restart Tomcat (to reload
> eXist on the correct
> port) otherwise several exceptions may crop up.
>
> Nicolas: Of course, I will contact Gina for the documentation.
>
>
> Kind regards,
> Prodromos
>
>

> Nicolas: Of course, I will contact Gina for the documentation.

Given packaging can't you patch the code/configuration for the specific
distribution? The
configuration should be tuned to accommodate the distribution method.

Just have a look at:
in eclipse right click on the project, select team > select create patch >
follow wizzard
save the file somewhere check it in under the packaging tree in the svn.

upon creating a release (candidate) appply the patch to the co/exported
project. build rpm
resp. deb. (depending on the patch you used.)

This whole process could be automated.

Any step you can take away from the user, you probably should as it is else a
step that
can(and will) fail.

If you need more pointers, you know where to find me.

Kind regards,

Michael






Archive powered by MHonArc 2.6.16.

Top of Page