Re: Moving from DEV to TEST to PROD servers.

I would like to hear too if there is any way Turnover could manage java
artifacts like jars,ears etc (storing as a BLOB in a FILE and a special
classloader?)

We use plain Java 6 and use the Endpoint.publish method (looking at using
Jetty under the covers). The address to publish to is read from the file
system. Then when inside the method invoked by the client you should be
able to hook into the code generated by the wizard, to get the automatically
generated program call.




-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Shalom Carmel
Sent: 4. august 2013 14:17
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Moving from DEV to TEST to PROD servers.

Hi,

A customer is using RDI's feature to create web services from rpgle
programs.
They have different servers for development, testing/qa and production.

The web services created by RDI are self-contained web apps with embedded
endpoints (IP addresses, server names, library lists) both in the config
files and in the created WSDL files.

There are obviously differences between the servers: Their IP addresses are
different, and the library lists are not the same. These differences are
today managed manually in an extremely tedious process.

They use Turnover to move the rpg code between the environments, but
currently move the EAR files manually. Afaik there is no Turnover feature to
deploy such web apps between different environments, or is there?

What are you doing in those cases? Run custom Ant/Maven scripts before
deployment?
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.