Use Cases for Petals-BC-Gateway

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History
h3. Running the use case

h4. Deploying Starting the consumer domain

With a first fresh installation of the Petals ESB ZIP archive exploded in directory '{{consumer-domain}}', launch the default standalone topology:
{code}

h4. Deploying Starting the provider domain

With a first fresh installation of the Petals ESB ZIP archive exploded in directory '{{provider-domain}}':
* configure ports to avoid conflicts with the ones of the consumer domain. Edit the file '{{topology.xml}}' and update values for '{{rmi-port}}' and '{{tcp-port}}', for example to '{{7710}}' and '{{7810}}',
* and, launch the default standalone topology:

{code}

h4. Deploying Petals service configurations

The following Petals artifacts must be deployed on the consumer domain:
{code}
petals-cli.sh -c -- deploy -u mvn:org.ow2.petals/petals-bc-soap/5.2.0-SNAPSHOT/zip
petals-cli.sh -c -- deploy -u mvn:org.ow2.petals/petals-bc-gateway/1.3.0-SNAPSHOT/zip
petals-cli.sh -c -- deploy -u mvn:org.ow2.petals.samples.gateway-soap-proxy/sa-gateway-soap-proxy-consumer-domain/1.0.0-SNAPSHOT/zip
{code}

And, the following Petals artifacts must be deployed on the provider domain:
{code}
petals-cli.sh -c -- deploy -u mvn:org.ow2.petals/petals-bc-soap/5.2.0-SNAPSHOT/zip
petals-cli.sh -c -- deploy -u mvn:org.ow2.petals/petals-bc-gateway/1.3.0-SNAPSHOT/zip
petals-cli.sh -c -- deploy -u mvn:org.ow2.petals.samples.gateway-soap-proxy/sa-gateway-soap-proxy-provider-domain/1.0.0-SNAPSHOT/zip
{code}

h1. Complex Use Cases