Happy Easter!

I try to add a new Service, with the same node that is used by the
esoemanager service. I get an unique constraint error. I'am confused.
Need I a separate spep for all apps? In which case I need more than
one spep nodes?

The ESOE Manager service is created by the esoestartup:

Service Name: ESOE Manager
Service Url: http://myserver.domain.com/esoemanager
nodes-> spep Identifier: http://myserver.domain.com/

I try to add the following Service:

Service Name: MyNewService
Service Url: http://myserver.domain.com/mynewapp
Service Identifier: http://myserver.domain.com/
SPEPNodeUrl: http://myserver.domain.com/

Best regards,
Jonas

Hello,

Thanks and same to everyone on the list.

You can either use the same SPEP software in which case you don't need
to do anything or you can use a separate spep instance. Service
identifiers need to be unique however if you choose to go the second option.

In the first your "mynewapp" is essentially considered to be part of the
esoemanager group of applications in terms of the SPEP which protects it.

In this scenario (using a seperate spep install you would need):

Service Url: http://myserver.domain.com/mynewapp
Service Identifier: http://myserver.domain.com/mynewapp
SPEPNodeUrl: http://myserver.domain.com/spep-mynewapp

Obviously spep.war would need to be renamed spep-mynewapp.war and
deployed, the values for spep.data etc would need to be obtained from
spepvars.config as described at
http://www.esoeproject.org/confluence/display/eu/Java+SPEP+Installati...

Hope that helps.

regards,
Bradley
--
Bradley Beddoes
Lead Software Architect
Intient Pty Ltd

http://www.intient.com