Sharper Image GT800 Spezifikationen PDF herunterladen (Seite 18)

LIVECYCLE ES4 OVERVIEW

Foundation

Last updated 1/15/2015

The application manager supports packaging the assets that are part of a LiveCycle application into a LiveCycle archive

file. The archive file facilitates the transfer of an application from development to staging to production.

When a LiveCycle application is deployed, all the assets within it are also deployed. The process of deploying some of

those assets results in services being registered in the service registry, which can be invoked by the Invocation

framework.

For example, when a process is deployed, a service entry is created in the service registry that allows the process to be

invoked as a service. If the service is published, a WSDL file is created and added to the service registry, along with the

necessary metadata that the LiveCycle SDK framework uses to invoke the service.

Service registry

The service registry is used at run time to resolve the name of a service to an actual endpoint in the service container.

Many different versions of a service can be deployed at any one time in the service registry. The Invocation framework,

along with version information provided by the calling application, is used to bind the correct version of the service.

Services require a service container to run, similar to how Enterprise JavaBeans (EJBs) require a J2EE container.

LiveCycle includes only one implementation of a service container. This implementation is responsible for managing

the life cycle of a service, including deploying it and ensuring that requests are sent to the correct service. The service

container is also responsible for managing documents that are consumed and produced by a service.

For more information about the service container, see Programming with LiveCycle.

Scripted deployment

Scripted deployment lets you automate the deployment of applications from a development environment to a staging

or production environment.

The contents of a LiveCycle archive are extended to include service configurations, endpoint information, and security

profiles. A set of sample scripts are available to use as a starting point when modifying environmental parameters.

With these scripts you can modify such parameters as port numbers and host names that differ from one environment

to another.

Common architectural foundation

Foundation provides a common architectural foundation that enables a solution component to participate in

processes. It provides a common invocation mechanism that ensures consistent access to components, services, and

processes. This access is accomplished using the following methods:

• Java API

• Web services

• Watched folders

• Flex Remoting Service

• Representational State Transfer (REST)

• Email

Foundation also provides a consistent set of public APIs and SPIs. Strongly-typed Java libraries are consistent

regardless of the transport protocol used (RMI or SOAP).

1 2 ... 13 14 15 16 17 18 19 20 21 22 23 ... 67 68

Keine Kommentare

Sharper Image GT800 Spezifikationen Seite 18