Isolated Site Support for Spotfire® Streaming

Basic outline:

1. Install str and possibly sb-hp-fix if desired.
2. Make sure access to Maven Central or a mirror of it is available. Go to a DMZ or an environment with necessary network access, if needed.
3. Either get into a StreamBase Command prompt, or, in the following commands, run epdev with an explicit path, such as C:\TIBCO\sb-cep\10.5\bin64\epdev.
4. For the cleanest results, use a settings file (which epdev will respect with its --settings option) that is dedicated to building your isolated support file by specifying a <localRepository> element.
5. Run epdev offline maven with --for-studio --building-isolated --archived-local-repository path-to-zip. Dropping -for-studio makes things go faster, but Studio wants to load sources of dependencies by default.
6. Make that isolated support zip available (network share, intranet, etc.).

For developers at the site:

1. Grab the isolated support zip.
2. Run epdev install maven with --isolated-support-file path-to-zip.

The process needs to be repeated with every new release. It is also advisable for every service pack.

Using a special settings file just for building the isolated support file for others has the following advantages:

1. Artifacts from your personal work will not be redistributed.
2. If you keep that repository around, it will accumulate support for past releases, so that the file you make will support more than just one release.
3. Also, since most artifacts are useful from release to release, building a new support file will go faster after you've built the first one.

If you encounter any problems using the --building-isolated --archived-local-repository or --isolated-support-file options, then it may be necessary to use the following procedure instead.

Whether you are using the default settings or a special settings file, let the location of the Maven repository (for example, $HOME/.m2) to be duplicated on the isolated machine be $LOCAL_REPO. Then:

1. Run epdev offline maven with --for-studio
2. Zip up the contents of $LOCAL_REPO/repository
3. Transport the zip file to the isolated machine
4. Unzip the zipped file into repository folder of local repository on the isolated machine

It's very common to see some errors when running epdev offline maven. This is because epdev offline maven is being very thorough and trying to obtain the artifacts for all possible Streaming adapters -- however, not all the artifacts are available in public repositories. Missing artifacts for adapters that aren't going to be used in a particular environment aren't actually a problem, through, and these errors may be ignored. A rough guideline is that is there are about a dozen errors, it's probably OK, but if there are hundreds, then something is very wrong, probably connectivity to a remote repository. See this KnowledgeBase article for more detail: https://support.tibco.com/s/article/DependencyResolutionException-errors-from-epdev-offline-maven