In this Page
Live on July 18, 2015
You may need to clear your browser cache before you log into the latest SnapLogic Elastic Integration Platform.
See the appropriate documentation for your browser:
You may see an Upgrade Notice dialog informing you that you will be logged out immediately to complete the update process. Because the SnapLogic Elastic Integration Platform consists of multiple applications, you will likely see this message multiple times.
Activity Log: The Activity Log provides a way for org admins to track changes to user accounts and assets within their organization.
The Activity Log will start capturing data at the time of deployment. No details for existing asset activities are available. |
The permissions for org admins has changed within Lifecycle Management. Org admins are no longer able to create assets in non-development phases. |
For information on other Snap updates, see the Summer 2015 section of Snap Updates, 2015.
Ultra tasks: If the pipeline is going to be processing HTTP requests from a FeedMaster, it should have one unlinked input and one or more outputs views If the ultra task
is just supposed to keep the pipeline running, it should not have any unlinked views.
Service accounts: when creating a user as a service account, you are now prompted to confirm that action.
Preview dialog: The Save as JSON button in the preview dialog has been replaced with a Download link at the top of the dialog.
Support for Java 1.8 impacts Groundplex installation. For Windows Snaplex installation, you will need to update your JRE to 1.8. For Linux, it is updated as part of the installation process.
Message of the Day has been renamed to User Notifications.
It is possible that another application already uses one of the jcc ports used by SnapLogic. As a result, the jcc will not complete a full start cycle.
The ports in question are as follows:
Function | Port | Protocol | Application |
---|---|---|---|
jcc's HTTPS | 8081 | tcp | McAfee Framework Service (FrameworkService.exe) |
FeedMaster's HTTPS | 8084 | tcp | Apache Tomcat server (Netbeans JSP servlets) |
FeedMaster's broker | 8089 | tcp | Splunk web-interface |
The workaround is to override the default port by assigning the following entries in the global.properties file to ports which are available:
for http port: jcc.jetty_port = 8x89
for https port: jcc.cc_secure_port = 8x81