Open topic with navigation

TIBCO GridServer® 7.1.0

# Deploying Services

GridServer uses Grid Libraries to distribute classes, libraries, and other resources to Engines. Grid Libraries provide a solution to the problem of distinct Services requiring different versions of the same resource. They provide the following features:

| • | Version control, including optional automatic selection of the most current version of a Grid Library.

| • | Resource upgrading without interrupting current Sessions.

| • | Specification of dependencies on other Grid Libraries.

| • | Specification of which C++ runtime to use and non-default JREs via dependencies.

| • | All-in-one packaging for JAR files, native libraries for multiple OSes, .NET assemblies, Command Service executables, R scripts, and Engine Hooks.

| • | Specification of Environment Variables and Java System properties.

| • | Engines that require different compiler support libraries can participate in the same Service Session.

| • | Parameterization of package configuration through the use of property substitution files.

The Resource Deployment feature replicates Grid Libraries from a Manager to Engines. In the simplest sense, this enables you to copy a set of bundled resources to each Engine to run a Service.

This section details how to use Grid Libraries for Service deployment to your GridServer installation.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO GridServer®
Subtopics

Copyright © 2001-2022. TIBCO Software Inc. All Rights Reserved.