Pom and settings.xml ref

This part of the docmentation provides more information on the possible manipulations that can be done using the maven definitions. This consists of properties defined in the settings.xml or pom.xml. Depending if this applies to all builds or a particular build you will adjust the values in one or the other location.

Generic POM Entries

The following sections are generic entries in all pom files:

Properties Section

The properties section is used to influence the maven plugin but also to make the pom-file more flexible for changes

        <properties>
                <maven-sonicesb-plugin.version>2013-RC4</maven-sonicesb-plugin.version>
                <sonicesb.version>2013</sonicesb.version>
                <targetJavaVersion>1.6</targetJavaVersion>
                <targetTestJavaVersion>1.6</targetTestJavaVersion>
                <compileDebug>true</compileDebug>
                <compileOptimize>false</compileOptimize>
                <forkMode>always</forkMode>
        </properties>

Distribution Management

        <distributionManagement>
                <repository>
                        <id>releases</id>
                        <name>Description of the repo</name>
                        <url>http://serverURL/releases</url>
                </repository>
                <snapshotRepository>
                        <id>snapshots</id>
                        <name>Description of the repo</name>
                        <url>http://serverURL/snapshots</url>
                </snapshotRepository>
                <site>
                        <id>site</id>
                        <name>Description of the repo</name>
                        <url>file:///var/www/html/docs/${project.groupId}/${project.artifactId}/${project.version}</url>
                </site>
        </distributionManagement>

SCM Section

        <scm>
                <connection>scm:svn:http://svnURL/${project.groupId}/${project.artifactId}/trunk</connection>
                <developerConnection>scm:svn:http://svnURL/${project.groupId}/${project.artifactId}/trunk</developerConnection>
        </scm>

The other sections are more dependent on the type of project you are building and are documented in more detail in those sections.

Domain override

In some cases, the workbench can be installed using a different Domain or connection URL. Reason for this could be the need to run both 7.6 and 2013 versions of the development environment.

In order to be able to distinguish, the following properties can be used:

Property Default Value Description
sonicesb.devDomainName Domain1 Domain name to connect to
sonicesb.devDomainUser Administrator Username for the connection
sonicesb.devDomainPassword Administrator Password to be used for the connection
sonicesb.devDomainUrl tcp://localhost:2506 The URL to connect to the domain

SDM Manipulations

During the SDM Creation phase the following behaviors can be manipulated:

Property Default Value Description
sonicesb.failOnValidationWarning false During the build, the plugin validates if all given parameters have a value. In case of a blank or missing, you can choose between a warning or a failure
sonicesb.isInlineGeneration true During the Build, this parameter indicates to generate the ESB Container content in the SDM Model. When false, it reverts to the previous generation of the container.xml file
sonicesb.forcePropertyGeneration false When overriden to True, a parameter properties file will be created as before. Some deployment tools are depending on this file to exist (BA)

Topology Project

For the topology project, the following properties can be set:

Property Default Value Description
sonicesb.topologyFile src/main/sonicesb/topology.csv Location to the place where the definition file is placed
sonicesb.topologyFileSeparationString ; Separator used in the csv file