Secure Delivery Center Common use Cases (ii)

July 23 software Distribution management artifact Secure Delivery Center Free Technology Exchange application, MyEclipse original manufacturers

distributing eclipse-based products with SDC

Distributing Eclipse (RCP)-based products in SDC is a simple task, but it requires some special steps. You can customize how products are distributed for product setup policies, or you can import your software and distribute it through SDC.

The overall steps include:

1. Set an access policy to customize the appearance of the installer, including your end-user license agreement.
2. Set the security policy to restrict the user's actions on the product.
3. Import your Eclipse products (plugins and features) as a third-party library.
4. Create an Eclipse IDE package with your policies, software, and branding.

Set access Policy

1. Create a new access policy called "My Eclipse Product".

2. Limit the platforms supported by the available products.

3. If the user you are sending is installed after a restrictive firewall, be sure to enable the bundled installer.

4. Set the default shortcut path to be your company name or similar organization name.

5. If you have, you can configure the background picture of your installer.

6. Place your end-User License agreement in the EULA area.

Set security Policy

1. Create a new security policy called "My Eclipse Product".

2. If you do not have a workspace or you want to lock the installation, you can create an RCP application:

• Turn off all transitions in the end-users option to prevent end-user changes
• Turn off the end user's update display to maintain a simple user experience
• Configure the time interval for update checks that are required based on the software rollout policy

3. If you are using the normal Eclipse workspace feature, and you want to allow normal software to be added to your product:

• Enable the appropriate end-user update options based on your needs
• If users want to install their own software, you can open the update display for them
• Configure the time interval for update checks that are required based on the software rollout policy

import your product as a third-party library

1. Select the third-party library in the Navigator and click the Add icon.

2. Select Import Existing Eclipse Update Site, and then click Next.

Note : If you do not set up a third party libraries signature, a signing certificate notification appears and you can ignore this notification.

Library Import Mode

3. Click the Add icon to enter a site or click the Browse_archive_site icon to navigate to one or more update sites to import, and then click Next.

4. Select the software and version that you want to provide in the library, and then click Next.

5. Enter the library name and version, and then click Next.

Create a package for your software

1. Create a new Eclipse IDE package and name your product.

2. In the overview option, set a short title for your product, which uses the same file name as the software release you are using.

3. Select the RCP delivery check box, which adds an RCP product label to the package settings.

Specify RCP distribution

4. Set the package icon to use your software, preferably using the 256x256 PNG format, such shortcuts for your product has a good brand effect.

5. In the SOFTWARE option, add the third-party library that you created. Make sure that your product plug-in and branding plug-in is included (if you want to include a custom splash screen).

Add a third-party library to a package

6. In the RCP Product products option, select the method that you want to distribute, based on the package or P2 lineup.

rcp product labels

7. Enter your RCP product information. Before adding RCP product information to the options, you must add your software to the package on the software option.

8. Select the policy you created in the configuration options:

Access policy:My Eclipse Product
Security Policy:My Eclipse Product

9. Submit and promote your package.

"Mid-year promotion" MyEclipse Spring 65 percent bottom price! 6.24-7.24! only

Secure Delivery Center Common use Cases (ii)