Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Stardust/Knowledge Base/Getting Started/Installation"

m
m
Line 3: Line 3:
 
The Process Workbench is based on the [http://www.eclipse.org Eclipse Platform] and consists of the combination of the basic Eclipse platform and a number of plug-ins which can be installed from the online update site. Currently the IPP plug-ins are only supported for the Eclipse version [http://www.eclipse.org/downloads/packages/eclipse-ide-java-and-report-developers/heliossr2 Eclipse Helios Sr2 (3.6.2)]. Please make sure to download exactly the version appropriate for your operating system. It’s recommended to download the bundle '''Eclipse IDE for Java and Report Developers''' to avoid downloading BIRT-related plug-ins at later point via Eclipse update site.  
 
The Process Workbench is based on the [http://www.eclipse.org Eclipse Platform] and consists of the combination of the basic Eclipse platform and a number of plug-ins which can be installed from the online update site. Currently the IPP plug-ins are only supported for the Eclipse version [http://www.eclipse.org/downloads/packages/eclipse-ide-java-and-report-developers/heliossr2 Eclipse Helios Sr2 (3.6.2)]. Please make sure to download exactly the version appropriate for your operating system. It’s recommended to download the bundle '''Eclipse IDE for Java and Report Developers''' to avoid downloading BIRT-related plug-ins at later point via Eclipse update site.  
  
After downloading, install Eclipse by unzipping it into a target folder of your choice. Start the Eclipse application. When the Eclipse IDE opens for the first time you are presented with a ''Welcome'' screen, which you may close.
+
After downloading, install Eclipse by unzipping it into a target folder of your choice. Start the Eclipse application. When the Eclipse IDE opens for the first time you are presented with a ''Welcome'' screen, which you may close.  
  
In order to use Collaborative Modeling feature you will be needing the VCS-Connector plug-in, which itself requires Subclipse 1.6.17. The fastest and most stable way to install Subclipse plug-ins is to download the local update site from [http://subclipse.tigris.org/files/documents/906/49028/site-1.6.18.zip here], extract it to your local drive and install it into Eclipse prior any Infinity Process Platform related installation activities.
+
In order to use Collaborative Modeling feature you will be needing the VCS-Connector plug-in, which itself requires Subclipse 1.6.17. The fastest and most stable way to install Subclipse plug-ins is to download the local update site from [http://subclipse.tigris.org/files/documents/906/49028/site-1.6.18.zip here], extract it to your local drive and install it into Eclipse prior any Infinity Process Platform related installation activities.  
  
 
<br>
 
<br>
  
# Go to Help &gt; Install New Software...
+
#Go to Help &gt; Install New Software...  
# Add new local update site Subclipse pointing to the location to where you have extracted Subclipse archive
+
#Add new local update site Subclipse pointing to the location to where you have extracted Subclipse archive  
# Chose newly created local update site and select plug-ins such as shown in screenshot below
+
#Chose newly created local update site and select plug-ins such as shown in screenshot below  
# Confirm all possible follow up screens
+
#Confirm all possible follow up screens  
# Restart Eclipse after installation
+
#Restart Eclipse after installation
  
 
<br>
 
<br>
Line 23: Line 23:
 
After installation of Subclipse plug-ins, Infintiy Process Platform related plug-ins can be installed.  
 
After installation of Subclipse plug-ins, Infintiy Process Platform related plug-ins can be installed.  
  
# Go to Help > Install New Software...
+
#Go to Help &gt; Install New Software...  
# Add new remote update site IPP pointing to https://infinity.sungard.com/repository/ipp-eclipse-features/  
+
#Add new remote update site IPP pointing to https://infinity.sungard.com/repository/ipp-eclipse-features/  
# Chose IPP remote update site and when asked for a login type in the credentials (e-mail/password) you used when registering at the Infinity Storefront  
+
#Chose IPP remote update site and when asked for a login type in the credentials (e-mail/password) you used when registering at the Infinity Storefront  
# Select Infinity Process Platform - Process Workbench 6.x
+
#Select Infinity Process Platform - Process Workbench 6.x  
# Confirm all possible follow up screens  
+
#Confirm all possible follow up screens  
# Restart Eclipse after installation
+
#Restart Eclipse after installation
  
 
<br>
 
<br>
  
[[Image:Installing Stardust via Eclipse update 01.png]]
+
[[Image:Installing Stardust via Eclipse update 01.png]]  
  
 
<br>
 
<br>
  
<p>'''Note:''' Select '''Infinity Process Platform Visual Rules Integration''' only if this functionality is required and '''Visual Rules 5 RN36-201012152047''' plug-in bundle has been installed up-front. If Subclipse plug-ins have not been installed already, please unselect '''Infinity Modeling VCS-Connector''' plug-in.</p>
+
'''Note:''' Select '''Infinity Process Platform Visual Rules Integration''' only if this functionality is required and '''Visual Rules 5 RN36-201012152047''' plug-in bundle has been installed up-front. If Subclipse plug-ins have not been installed already, please unselect '''Infinity Modeling VCS-Connector''' plug-in.
  
<p>'''Note:''' Alternatively you can install Infinity Process Platform via local update site. For this you have to download the artifacts from the repository under https://infinity.sungard.com/repository/ipp-eclipse-features/ipp-6.0.2/offlineSite.zip.
+
Screenshot: Login screen
Replace the version number part of the URL according to your needs.</p>
+
  
 +
[[Image:Installing Stardust via Eclipse update 04.png]]
  
 
<br>
 
<br>
  
<p>Screenshot: Login screen</p>
+
Screenshot: Selected plug-ins screen
[[Image:Installing Stardust via Eclipse update 04.png]]
+
  
<br>
 
 
<p>Screenshot: Selected plug-ins screen</p>
 
 
[[Image:Installing Stardust via Eclipse update 05.png]]  
 
[[Image:Installing Stardust via Eclipse update 05.png]]  
  
 
<br>
 
<br>
  
<p>Screenshot: Review screen</p>
+
Screenshot: Review screen
'''[[Image:Installing Stardust via Eclipse update 06.png]]'''
+
 
 +
'''[[Image:Installing Stardust via Eclipse update 06.png]]'''  
  
 
<br>
 
<br>
  
<p>Screenshot: License Agreement screen</p>
+
Screenshot: License Agreement screen
'''[[Image:Installing Stardust via Eclipse update 07.png]]'''
+
 
 +
'''[[Image:Installing Stardust via Eclipse update 07.png]]'''  
  
 
<br>
 
<br>
  
<p>Screenshot: Installation progress screen</p>
+
Screenshot: Installation progress screen
'''[[Image:Installing Stardust via Eclipse update 08.png]]'''
+
 
 +
'''[[Image:Installing Stardust via Eclipse update 08.png]]'''  
  
 
Once installation is finished, a dialog appears suggesting to restart, which you should do. The Process Workbench requires a license file to be present. To load it, select '''Preferences''' and go to the '''Infinity''' section. Type the path to the license file or click '''Browse''' to locate it. Click '''Apply''' or '''OK.'''  
 
Once installation is finished, a dialog appears suggesting to restart, which you should do. The Process Workbench requires a license file to be present. To load it, select '''Preferences''' and go to the '''Infinity''' section. Type the path to the license file or click '''Browse''' to locate it. Click '''Apply''' or '''OK.'''  
Line 71: Line 70:
 
[[Image:Installing Stardust via Eclipse update 09.png]]'''<br>'''
 
[[Image:Installing Stardust via Eclipse update 09.png]]'''<br>'''
  
Turn to the integrated documentation to learn more about the Process Workbench. The included documentation for the Process Workbench can be found under the '''Help &gt; Help Contents''' menu item and then selecting the chapter for [[STP/Stardust/KnowledgeBase#Product_Documentation|'''Infinity Process Platform Documentation''']].  
+
'''Note:''' Alternatively you can install Infinity Process Platform via local update site. For this you have to download the artifacts from the repository under [https://infinity.sungard.com/repository/ipp-eclipse-features/ipp-6.0.2/offlineSite.zip https://infinity.sungard.com/repository/ipp-eclipse-features/ipp-6.0.2/offlineSite.zip] and extract it to your local disk. Replace the version number part of the URL according to your needs.
 +
 
 +
<br>
 +
 
 +
#Go to Help &gt; Install New Software...
 +
#Add new local update site IPP pointing to the location to where you have extracted offlineSite.zip archive
 +
#Chose created local update site and select Infinity Process Platform - Process Workbench 6.x
 +
#Confirm all possible follow up screens
 +
#Restart Eclipse after installation
 +
 
 +
<br>
 +
 
 +
Turn to the integrated documentation to learn more about the Process Workbench. The included documentation for the Process Workbench can be found under the '''Help &gt; Help Contents''' menu item and then selecting the chapter for [[STP/Stardust/KnowledgeBase#Product_Documentation|'''Infinity Process Platform Documentation''']].
  
Enjoy using Infinity Process Workbench until you can use it as Stardust as an even more integral part of the Eclipse project!<br>
+
Enjoy using Infinity Process Workbench until you can use it as Stardust as an even more integral part of the Eclipse project!
  
 
== Receiving Artifacts from the Maven Repository  ==
 
== Receiving Artifacts from the Maven Repository  ==
Line 99: Line 110:
 
You can use Apache Ivy ant tasks to receive the artifacts and build your work environment. For details on using Ivy, please refer to the [http://ant.apache.org/ivy/ Apache Ivy Site].  
 
You can use Apache Ivy ant tasks to receive the artifacts and build your work environment. For details on using Ivy, please refer to the [http://ant.apache.org/ivy/ Apache Ivy Site].  
  
You can use the following code snippets for the files needed to be configured:<br>  
+
You can use the following code snippets for the files needed to be configured:<br>
  
'''ivy.xml'''<br>  
+
'''ivy.xml'''<br>
 
<pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
 
<pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
 
&lt;ivy-module version="2.0" xmlns:m="http://ant.apache.org/ivy/maven" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 
&lt;ivy-module version="2.0" xmlns:m="http://ant.apache.org/ivy/maven" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Line 115: Line 126:
 
   &lt;/dependencies&gt;
 
   &lt;/dependencies&gt;
 
&lt;/ivy-module&gt;
 
&lt;/ivy-module&gt;
</pre>  
+
</pre>
'''|ivy-settings.xml'''<br>  
+
'''|ivy-settings.xml'''<br>
 
<pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
 
<pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
 
&lt;ivysettings&gt;
 
&lt;ivysettings&gt;
Line 129: Line 140:
 
   &lt;settings defaultResolver="ipp-releases"/&gt;
 
   &lt;settings defaultResolver="ipp-releases"/&gt;
 
&lt;/ivysettings&gt;
 
&lt;/ivysettings&gt;
</pre>  
+
</pre>
 
'''build.xml'''  
 
'''build.xml'''  
 
<pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
 
<pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
Line 167: Line 178:
 
&lt;/target&gt;
 
&lt;/target&gt;
 
&lt;/project&gt;
 
&lt;/project&gt;
</pre>  
+
</pre>
 
Run the build file to retrieve the <tt>ipp-tools.zip</tt> archive. Please take care to use the right proxy settings in your Java environment.  
 
Run the build file to retrieve the <tt>ipp-tools.zip</tt> archive. Please take care to use the right proxy settings in your Java environment.  
  
Line 178: Line 189:
 
m2.server.auth.realm = Artifactory Realm
 
m2.server.auth.realm = Artifactory Realm
 
m2.server.auth.username = &lt;i&gt;username&lt;/i&gt;
 
m2.server.auth.username = &lt;i&gt;username&lt;/i&gt;
m2.server.auth.password = &lt;i&gt;password&lt;/i&gt;</pre>  
+
m2.server.auth.password = &lt;i&gt;password&lt;/i&gt;</pre>
All needed Ivy files are downloaded as well:<br>  
+
All needed Ivy files are downloaded as well:<br>
  
 
*'''ivy.xml''' - to declare the project's modules and dependencies.  
 
*'''ivy.xml''' - to declare the project's modules and dependencies.  
Line 188: Line 199:
  
 
All artifacts like documentation, runtime, client scripts etc., will be downloaded. To get an overview about the runtime dependencies, you can execute the ANT target <tt>report</tt> of the <tt>build.xml</tt> file. Per default, the latest integration is used to retrieve the appropriate version. Thus, you always get the latest version, that can be found in the repository. If you are interested in a specific version, you can either pass the version via a parameter, e.g.  
 
All artifacts like documentation, runtime, client scripts etc., will be downloaded. To get an overview about the runtime dependencies, you can execute the ANT target <tt>report</tt> of the <tt>build.xml</tt> file. Per default, the latest integration is used to retrieve the appropriate version. Thus, you always get the latest version, that can be found in the repository. If you are interested in a specific version, you can either pass the version via a parameter, e.g.  
<pre>&lt;tt&gt;-Dipp.version=6.0.2&lt;/tt&gt;</pre>  
+
<pre>&lt;tt&gt;-Dipp.version=6.0.2&lt;/tt&gt;</pre>
 
or you can permanently store this parameter in the <tt>etc/build.properties</tt> file.  
 
or you can permanently store this parameter in the <tt>etc/build.properties</tt> file.  
  
Line 203: Line 214:
 
root="/ipp-3rd-party-nondistributable"
 
root="/ipp-3rd-party-nondistributable"
 
m2compatible="true" cache="ipp-tools-ivy-cache"/&gt;
 
m2compatible="true" cache="ipp-tools-ivy-cache"/&gt;
</pre>  
+
</pre>
 
In the <tt>chain</tt> section, add a reference to this repository:  
 
In the <tt>chain</tt> section, add a reference to this repository:  
 
<pre>&lt;chain name="pull-ipp-deps"&gt;
 
<pre>&lt;chain name="pull-ipp-deps"&gt;
Line 210: Line 221:
 
...
 
...
 
&lt;/chain&gt;
 
&lt;/chain&gt;
</pre>  
+
</pre>
 
== Upgrading and Downgrading Installed Features  ==
 
== Upgrading and Downgrading Installed Features  ==
  
You have the option to upgrade or downgrade installed features. The following sections describe the necessary steps to be performed:<br>  
+
You have the option to upgrade or downgrade installed features. The following sections describe the necessary steps to be performed:<br>
  
 
*[[#up|Upgrading Features]]  
 
*[[#up|Upgrading Features]]  
Line 220: Line 231:
 
=== Upgrading Features  ===
 
=== Upgrading Features  ===
  
To upgrade your installed features to a later version provided in the repository, perform the following steps:<br>  
+
To upgrade your installed features to a later version provided in the repository, perform the following steps:<br>
  
 
#In the main menu, select '''Help &gt; Check for Updates'''.
 
#In the main menu, select '''Help &gt; Check for Updates'''.
  
[[Image:Check-for-updates.png]]<br>  
+
[[Image:Check-for-updates.png]]<br>
  
 
#The '''Available Updates''' dialog opens. Select the updates you like to install. In the '''Version''' column, the newest version to update to is displayed.
 
#The '''Available Updates''' dialog opens. Select the updates you like to install. In the '''Version''' column, the newest version to update to is displayed.
  
[[Image:Stardust Select-updates.png]]<br>  
+
[[Image:Stardust Select-updates.png]]<br>
  
#Review and confirm your selected updates and click '''Next'''.<br>  
+
#Review and confirm your selected updates and click '''Next'''.<br>
 
#Accept the license and select '''Finish'''.  
 
#Accept the license and select '''Finish'''.  
 
#Restart Eclipse.
 
#Restart Eclipse.
  
<br>  
+
<br>
  
 
If upgrading to a new version in an already configured environment, also take care to perform the necessary steps to upgrade your Web project and model accordingly, as described in chapter [[Upgrading to Later Versions|Upgrading to Later Versions]].  
 
If upgrading to a new version in an already configured environment, also take care to perform the necessary steps to upgrade your Web project and model accordingly, as described in chapter [[Upgrading to Later Versions|Upgrading to Later Versions]].  
  
 
<br>
 
<br>

Revision as of 10:26, 8 November 2011

Eclipse Update Site

The Process Workbench is based on the Eclipse Platform and consists of the combination of the basic Eclipse platform and a number of plug-ins which can be installed from the online update site. Currently the IPP plug-ins are only supported for the Eclipse version Eclipse Helios Sr2 (3.6.2). Please make sure to download exactly the version appropriate for your operating system. It’s recommended to download the bundle Eclipse IDE for Java and Report Developers to avoid downloading BIRT-related plug-ins at later point via Eclipse update site.

After downloading, install Eclipse by unzipping it into a target folder of your choice. Start the Eclipse application. When the Eclipse IDE opens for the first time you are presented with a Welcome screen, which you may close.

In order to use Collaborative Modeling feature you will be needing the VCS-Connector plug-in, which itself requires Subclipse 1.6.17. The fastest and most stable way to install Subclipse plug-ins is to download the local update site from here, extract it to your local drive and install it into Eclipse prior any Infinity Process Platform related installation activities.


  1. Go to Help > Install New Software...
  2. Add new local update site Subclipse pointing to the location to where you have extracted Subclipse archive
  3. Chose newly created local update site and select plug-ins such as shown in screenshot below
  4. Confirm all possible follow up screens
  5. Restart Eclipse after installation


Installing Stardust via Eclipse update 02.png


After installation of Subclipse plug-ins, Infintiy Process Platform related plug-ins can be installed.

  1. Go to Help > Install New Software...
  2. Add new remote update site IPP pointing to https://infinity.sungard.com/repository/ipp-eclipse-features/
  3. Chose IPP remote update site and when asked for a login type in the credentials (e-mail/password) you used when registering at the Infinity Storefront
  4. Select Infinity Process Platform - Process Workbench 6.x
  5. Confirm all possible follow up screens
  6. Restart Eclipse after installation


Installing Stardust via Eclipse update 01.png


Note: Select Infinity Process Platform Visual Rules Integration only if this functionality is required and Visual Rules 5 RN36-201012152047 plug-in bundle has been installed up-front. If Subclipse plug-ins have not been installed already, please unselect Infinity Modeling VCS-Connector plug-in.

Screenshot: Login screen

Installing Stardust via Eclipse update 04.png


Screenshot: Selected plug-ins screen

Installing Stardust via Eclipse update 05.png


Screenshot: Review screen

Installing Stardust via Eclipse update 06.png


Screenshot: License Agreement screen

Installing Stardust via Eclipse update 07.png


Screenshot: Installation progress screen

Installing Stardust via Eclipse update 08.png

Once installation is finished, a dialog appears suggesting to restart, which you should do. The Process Workbench requires a license file to be present. To load it, select Preferences and go to the Infinity section. Type the path to the license file or click Browse to locate it. Click Apply or OK.

Installing Stardust via Eclipse update 09.png

Note: Alternatively you can install Infinity Process Platform via local update site. For this you have to download the artifacts from the repository under https://infinity.sungard.com/repository/ipp-eclipse-features/ipp-6.0.2/offlineSite.zip and extract it to your local disk. Replace the version number part of the URL according to your needs.


  1. Go to Help > Install New Software...
  2. Add new local update site IPP pointing to the location to where you have extracted offlineSite.zip archive
  3. Chose created local update site and select Infinity Process Platform - Process Workbench 6.x
  4. Confirm all possible follow up screens
  5. Restart Eclipse after installation


Turn to the integrated documentation to learn more about the Process Workbench. The included documentation for the Process Workbench can be found under the Help > Help Contents menu item and then selecting the chapter for Infinity Process Platform Documentation.

Enjoy using Infinity Process Workbench until you can use it as Stardust as an even more integral part of the Eclipse project!

Receiving Artifacts from the Maven Repository

Additionally to the Workbench Artifacts, Infinity provides the following artifacts and scripts:

  • Runtime artifacts
  • Client scripts
  • Spring configurations
  • Web artifacts like deployable archives and configuration snippets
  • Infinity Scan

These components are available by the ipp-tools artifact. You can download this artifact directly from the artifactory from the following location:

https://infinity.sungard.com/repository/ipp-libs/com/infinity/bpm/ipp-tools/

or by an Ivy integrated Ant task as described in the following section.

Retrieving the Artifacts via Ivy Integrated Ant Tasks

You can use Apache Ivy ant tasks to receive the artifacts and build your work environment. For details on using Ivy, please refer to the Apache Ivy Site.

You can use the following code snippets for the files needed to be configured:

ivy.xml

<?xml version="1.0" encoding="UTF-8"?>
<ivy-module version="2.0" xmlns:m="http://ant.apache.org/ivy/maven" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd">
  <info organisation="<organisation.name>" module="<ipp-client-tool>" revision="<x.y.z>" />
  <configurations>
    <conf name="ipp-tools" />
  </configurations>
  <dependencies>
    <dependency org="com.infinity.bpm" name="ipp-tools" rev="" conf="ipp-tools->default">
      <artifact name="ipp-tools" type="zip"/>
    </dependency>
  </dependencies>
</ivy-module>

|ivy-settings.xml

<?xml version="1.0" encoding="UTF-8"?>
<ivysettings>
  <property name="ipp.m2.repository" value="https://internal.csa.sungard.com/artifactory" override="false"/>
  <property name="default.ivy.cache" value="/.cache" override="false"/>
  <caches>
    <cache name="ipp-tools-ivy-cache" basedir="" useOrigin="true" />
  </caches>
  <resolvers>
    <ibiblio name="ipp-releases" root="/ipp-libs" m2compatible="true" cache="ipp-tools-ivy-cache"/>
  </resolvers>
  <settings defaultResolver="ipp-releases"/>
</ivysettings>

build.xml

<?xml version="1.0" encoding="UTF-8"?>
<project name="retrieve-ipp-tools" default="retrieve-ipp-tools" xmlns:ivy="antlib:org.apache.ivy.ant">
<property name="ivy.install.version" value="2.2.0" />
<property name="ivy.jar.dir" value="/ivy" />
<property name="ivy.jar.file" value="/ivy.jar" />
<property name="ivy.settings.file" value="ivy-settings.xml" />
<property name="m2.server.host" value="internal.csa.sungard.com" />
<property name="m2.server.auth.realm" value="Artifactory Realm" />
<property name="m2.server.auth.username" value="<i>username</i>" />
<property name="m2.server.auth.password" value="<i>password</i>" />
<property name="ipp.version" value="latest.integration" />
<!-- Downloading ivy -->
<target name="download-ivy" unless="skip.download" description="Downloading ivy">
  <mkdir dir=""/>
  <get src="http://repo1.maven.org/maven2/org/apache/ivy/ivy//ivy-.jar" dest="" usetimestamp="true"/>
</target>
<!-- Installing ivy -->
<target name="install-ivy" depends="download-ivy" description="Installing ivy">
  <path id="ivy.lib.path">
    <fileset dir="" includes="*.jar"/>
  </path>
  <taskdef resource="org/apache/ivy/ant/antlib.xml" uri="antlib:org.apache.ivy.ant" classpathref="ivy.lib.path"/>
</target>
<!-- Setting up ivy -->
<target name="setup-ivy" depends="install-ivy" description="Setting up ivy">
  <ivy:settings id="ivy.instance" file="">
    <ivy:credentials host="" realm="" username="" passwd="" />
  </ivy:settings>
</target>
<!-- Retrieving IPP Tools -->
<target name="retrieve-ipp-tools" depends="setup-ivy" description="Retrieving IPP Tools">
  <ivy:resolve/>
  <ivy:retrieve conf="ipp-tools" pattern="[artifact].[ext]" type="zip"/>
  <unzip dest="." src="ipp-tools.zip"/>
</target>
</project>

Run the build file to retrieve the ipp-tools.zip archive. Please take care to use the right proxy settings in your Java environment.

Building your Work Environment via Ivy Integrated Ant Tasks

Unzip the downloaded or created ipp-tools.zip file.

After doing so, you find a ipp-ivy-cred.properties file in the etc folder. Open this file and set the appropriate user and password, e.g.:

m2.server.host = internal.csa.sungard.com
m2.server.auth.realm = Artifactory Realm
m2.server.auth.username = <i>username</i>
m2.server.auth.password = <i>password</i>

All needed Ivy files are downloaded as well:

  • ivy.xml - to declare the project's modules and dependencies.
  • ivy-settings.xml - to configure artifact resolution.
  • build.xml - to execute the ANT tasks for artifact resolution.

Now execute the ANT target retrieve-ipp-tools, which you find in the provided build.xml file.

All artifacts like documentation, runtime, client scripts etc., will be downloaded. To get an overview about the runtime dependencies, you can execute the ANT target report of the build.xml file. Per default, the latest integration is used to retrieve the appropriate version. Thus, you always get the latest version, that can be found in the repository. If you are interested in a specific version, you can either pass the version via a parameter, e.g.

<tt>-Dipp.version=6.0.2</tt>

or you can permanently store this parameter in the etc/build.properties file.

Including Third party Libraries

You need to set up a custom repository to include the following third party libraries:

  • jai-imageio-1.1.jar - javax.media.group-id
  • stax-ex-1.0.jar - org.jvnet.staxex
  • streambuffer-0.4.jar - com.sun.xml.stream.buffer

In your ivy-settings.xml, add your custom repository in the resolvers section, e.g.:

<ibiblio name="ipp-nondistributable"
root="/ipp-3rd-party-nondistributable"
m2compatible="true" cache="ipp-tools-ivy-cache"/>

In the chain section, add a reference to this repository:

<chain name="pull-ipp-deps">
...
<resolver ref="ipp-nondistributable" />
...
</chain>

Upgrading and Downgrading Installed Features

You have the option to upgrade or downgrade installed features. The following sections describe the necessary steps to be performed:

Upgrading Features

To upgrade your installed features to a later version provided in the repository, perform the following steps:

  1. In the main menu, select Help > Check for Updates.

Check-for-updates.png

  1. The Available Updates dialog opens. Select the updates you like to install. In the Version column, the newest version to update to is displayed.

Stardust Select-updates.png

  1. Review and confirm your selected updates and click Next.
  2. Accept the license and select Finish.
  3. Restart Eclipse.


If upgrading to a new version in an already configured environment, also take care to perform the necessary steps to upgrade your Web project and model accordingly, as described in chapter Upgrading to Later Versions.


Back to the top