On-Demand Delivery packages allow you to deliver Secure Marketplace catalogs and/or security policy enforcement to existing Eclipse IDE installations. In the On-Demand Packages diagram below, you see the Eclipse IDE is obtained from an outside source and installed apart from using SDC. An admin installs add-on software onto the secure server and delivers Secure Marketplace catalogs of tested and approved software, as well as security policies, to Eclipse users.
SDC's Secure Marketplaces give your end users the flexibility to install add-on software from a catalog that is securely accessed from behind your firewall. Because administrators can specify the software available in the catalog, you are able to control access to software, thus creating your own marketplace catalog of approved add-on software.
Not only can secure marketplace catalogs be used with software packages you create and distribute using SDC, but you can include Secure Marketplace catalogs in on-demand delivery packages for use with Eclipse installations that aren't managed through SDC.
Delegate team administration tasks by designating some end users as group administrators. These group admins are given access to the Admin Console, which provides them rights to make package changes for their team. The group administrator can change and promote add-on libraries and the packages in only their assigned delivery group.
If you think you might want to re-promote a package after subsequent promotions occur, save it as a snapshot. Take a snapshot of the most recent version that has current installers. Snapshots appear on the portal page for the group(s) associated with the package, and can be installed at any time.
When selecting add-on software, there are several add-ons that have additional supporting components you generally want to install. When you choose these add-ons from a certified popular software pack, the supporting components are automatically added, as well. In the example below, SVNKit for Subclipse was added from the Certified Popular Software pack. This triggered both the install of Subclipse and the inclusion of the supporting components.
License usage is now more detailed in that you can view the specific developers using a license. On the Licenses tab of the System Administration page, the details can be shown for each license listed. License usage is tracked by developer, rather than by machine (up to three machines per developer).
The External Users Extension allows you to use your company's name lookup service, e.g. LDAP, instead of having the SDC server keep track of your user accounts. When you install an implementation of the External Users Extension, the entire SDC system changes in the following ways:
When configuring a package, you can specify the level of authentication required to access the package. There are four levels of access control for a package - everyone, authenticated, restricted, and admins only.
Everyone - anyone can view and install the package from the portal.
Authenticated - requires a password on the portal and in the installed package to install and use the package.
Restricted - requires a user to be a member of a group associated with the package.
Admins Only - indicates that only users logged in as a system or group admin have access to the package. This is useful for testing packages among your administrators before giving your users access to the package.
For groups, the Public/Private toggle allows you to specify that the group is private and requires authentication to access. The default is Public. Authentication of groups relates to package authentication. If a user is a member of a group but doesn't have access to a package based on package authentication level, the package will not appear on the group page for that user. If a group is set to private and a user is not included in the group users list, the user does not have access to the group page.
As part of the Access Policy settings, choose a configuration to assist in web and network installer optimization. If most users are on a local network, select Speedy Networks. If many users are accessing via a WAN, select Powerful Computers.
SDC supports a special .wrkspc file that allows delivery of arbitrary files into your workspaces. This task can be used for dropping down extra files into the .metadata/ area for plugins that do not work with standard preferences. Incremental changes are done to the files by replacing the .wrkspc file.
Package setup now includes a Notifications tab for sending messages to the package users when you promote changes. Notifications can be critical, warning, or informative messages. Messages can be valid for a specified date range, which helps manage the visibility of notifications.
Support for Java 1.7 enables your users to update to the latest Java without fear of interrupting their secure deployment of IDEs. Additionally, targeted performance enhancements in SDC make it the fastest platform for deploying software via Java 1.7.