Here are some of the highlights from the April 2017 release. For the complete list, see:
Custom Libraries (a.k.a. JAR Management)
This is a significant new feature that allows you to install and manage custom libraries such as connector drivers and third party custom script libraries through the AtomSphere UI without requiring access to the runtime installation directory.
It works like this:
- Administrators can upload jar files at the account-level make them available to process developers.
- Process developers can reference those files using a new Custom Library component.
- The Custom Library component can be managed and deployed to environments and Atoms in the same way as process or certificate components, for example.
- You can now use custom connector drivers and script libraries in the Dell Boomi Atom Clouds
- You do not need physical access to the local Atom server/installation directory (i.e. your operations team doesn't have to grant you access)
- You can manage the libraries yourself (i.e. you don't have to get your operations team involved) and include them as part of your normal process deployment life cycle
A few notable observations:
- Only *.jar files are supported.
- In most cases, the Atom does NOT need to be restarted for the new library to be registered
- This feature is available to all account editions
You do not explicitly reference the Custom Library component in the process configuration such as Connection component or Data Process shape or map function. It is maintained and deployed independently, essentially the same as if you were adding the library to the Atom installation directory manually.
For more information see:
Atom Management: Read Only Access (continued)
The work started in February 2017 to provide read-only access to the various panels in Atom Management continues in this release. A number of panels now support read-only access including:
- Account Properties
- Environment Extensions (most types)
- Shared Queue Server
- Shared Web Server
Look for read-only access for the remaining panels including Deployed Processes and Data Map Extensions coming soon.
This release also fixes a bug whereby a user with Atom Management Read Only privileges could still modify Environment-level settings.
Trading Partner Management
HTTP Communication Type
Trading partner shapes can now receive, get, and send data via HTTP. The Web Services Listener (i.e. the shared web server) and HTTP Client connectors are now available as communication types within the Trading Partner (and Communication Channel) components. While many document standards such as X12 and EDIFACT are often exchanged via AS2 or FTP, this sets the stage to exchange other standards including RosettaNet and "custom" standards in the not too distant future.
Other B2B Features...
Be sure to follow this blog series for deep dives on the new trading partner management features introduced in the previous release. Here are the most recent posts:
- Trading Partner Management Part 2: Processing Groups - Groups and Membership
- Trading Partner Management Part 3: Processing Groups - Advanced Routing
Two advanced options allow additional control over the request behavior when interacting with certain web servers. They may apply if the web server is configured to interact with end users directly (via a browser) vs. a programmatic client such as AtomSphere.
- Set Cookie scope - In the Connection component, configure if cookies returned by the server are remembered "Globally" (across all the processes running in the Atom; technically per JVM), remembered for the given "Connector Shape" (that is, for the single connector shape's execution within a single process), or ignored altogether.
- Response Headers to Use in Subsequent Requests (a.k.a. server reflected headers) - In the Operation component, specify any response headers returned by the server during the login/authentication handshake that should be automatically included in any subsequent requests (i.e. the actual call to get/send the payload) within the context of the given connector shape execution. This is commonly used to forward CSRF (Cross-Site Request Forgery) tokens received by the server.
The connector now supports version 2016.2.
Master Data Management
It's all about governance and insights! This release includes a couple of enhancements that continue to provide MDM admins and stewards more control in establishing and enforcing governance rules as well as additional tools to analyze historical data.
- Approvals for golden record end-dating - Similar to when a new golden record is created, a manual approval can now be required for when a given source attempts to end-date (effectively soft delete) a golden record. This approval can also be performed programmatically via the platform API if data stewards are working from an external dashboard.
- More historical reporting options - Custom date ranges and statistics such as max/min and median values give data analysts additional ways to slice and dice the MDM metrics.
New Learning Management System!
We recently launched a brand new Learning Management System (LMS). The LMS is your new destination to enroll in instructor-led and on-demand training content and tracks your progress through courses and certifications.