Sharper Image GT800 Especificações descarregar pdf (Página 17)

LIVECYCLE ES4 OVERVIEW

Foundation

Last updated 1/15/2015

Using the Job Manager service API, developers can do these tasks:

• Create a new asynchronous job using the specified invocation request.

• Complete an existing job using the specified invocation response.

• Terminate, suspend, or resume an existing job identified by the specified job ID.

• Get the job ID that represents the status of a long-lived process. The job status indicates whether a job was queued,

running, completed, terminated, suspended, or resumed. The status can also indicate whether a request was issued

to complete, terminate, suspend, or resume a job.

For more information about invoking long-lived processes, see Programming with LiveCycle

For information about managing processes using Administration Console, see the LiveCycle Administration

Console Help.

Process archive and deletion

LiveCycle now provides a set of APIs and sample scripts so that administrators can delete completed processes,

including the ability to define queries. An example is deleting all purchase order processes with a value under $10,000

completed more than 6 months ago. With this feature, you can better manage the process data and audit information

within the database.

Repository and service registry

The repository provides the capability to manage the assets that developers create as part of their LiveCycle

applications.

Developers can access the repository by using the Form Design perspective in Workbench or programmatically using

the repository API. A developer must be granted access before accessing the repository. Each time a developer uses

Workbench, a connection to the repository is made. The repository is exposed as a hierarchical directory structure.

One or more developers can share the repository from Workbench.

Staging and production systems each have their own repository. For example, an organization’s quality assurance team

tests a service in their staging environment. When the tests are successful, the team deploys the service into their

production environment. When a service is deployed into production, it has no dependency on any design-time assets

in the staging environment’s repository. The organization can optionally use the service registry’s access control

mechanisms to restrict access to the service deployed in the production environment. This enables the organization to

pilot a deployment with a restricted group of users.

Registering assets and services

The repository provides storage capabilities. When a developer creates an application, the developer can deploy the

assets in the repository instead of deploying them on a file system. The assets may consist of XML forms, PDF forms

(including Acrobat forms), fragments, images, processes, profiles, policies, DDX files, XML schemas, WSDL files, SWF

files, and test data.

The repository tracks the version of each asset in a LiveCycle application. At run time, services can retrieve assets from

the repository as part of completing an automated business process.

Creating LiveCycle applications

The repository maintains dependency relationships among all the assets it manages. LiveCycle uses these dependency

relationships to assemble all the necessary assets into a LiveCycle application.

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

Sem comentários

Sharper Image GT800 Especificações Página 17