Importing resources, processes, and events to applications
|
Import legacy processes, resources, and events to add them
to applications in the Applications view. For each legacy item,
a corresponding asset is created in a target application.
The following rules apply when importing legacy items to applications:
-
You can import only one version of a process to an application
version. Create multiple applications (or application versions)
to import multiple versions of a process.
-
You can import a process, resource, or event to multiple
applications to create multiple copies.
-
Applications can include either legacy items or assets created
using LiveCycle ES2.5. Do not place both legacy items and LiveCycle
ES2.5 assets in the same application.
-
In an application, process names must be unique. If the process
you are importing has the same name of an existing process, even
if their deployment IDs are different, the import operation fails.
-
In an application, Deployment IDs of processes must be unique.
If the process you are importing has a different name but the same
Deployment ID of an existing process, the import operation fails.
Application names and folder names have the following restrictions:
-
Names can have a maximum length of 40 characters.
-
The total number of characters in the path of an asset cannot
exceed 256.
-
Names cannot include control characters (characters that
have an ASCII value that is less than 32).
-
Names cannot include any of the following characters: "/",
"\", "+", "$", "?", "*", ":", "|", "<", ">", ",", and the
tab key.
If your legacy resources use a folder structure that conflicts
with these restrictions, modify the folder structure before importing.
Not adhering to these restrictions can cause resources to be inaccessible.
You can import legacy items from the run-time environment, the
file system, and LiveCycle ES archives.
Importing from the run-time environment
Import legacy items from the run-time environment to create
representations of them in the Applications view. The resultant
application assets are directly linked to the instances in the run-time
environment.
Typically, you import legacy items from the run-time environment
to edit them. For example, to edit a process version that exists
in the run-time environment, import it to an application and then
open it. (See
Maintaining legacy run-time instances
.)
After importing, the locations in the run-time environment do
not change. Consequently, references between imported items are
persisted regardless of which application they belong to. Therefore,
legacy applications continue to execute successfully.
Import legacy items from the run-time environment:
-
Click
File > Import.
-
Under LiveCycle Runtime Content, select Event, Process, or
Resource, depending on the type of item you are importing, and then
click Next.
-
Select the event types, resources, or process versions to
import:
-
Events:
Select one or more event types.
To select multiple event types, expand the event categories and
Ctrl+click.
-
Processes:
Select one or more process versions. To
select multiple process versions, expand the process groups and
processes and then Ctrl+click.
-
Resources:
Select resources or resource folders. If
you select a folder, the entire contents, including subfolders and
resources, are imported. Ctrl+click to select multiple folders or
resources.
-
In the Enter Or Select Import Location box, specify the target
location for the selected items, and then click Finish.
Importing from the file system
Import LiveCycle ES items from the file system when you
want to use them in LiveCycle ES2.5 applications. For example, import
processes that you exported to XML files from the LiveCycle ES environment.
You can import individual files or entire folders. You can also
duplicate the file structure on the file system in the application.
After you import files with long file structures, verify that
the path does not exceed the 256-character limit. When the imported
file has a resulting path in the application that exceeds the 256-character
limit, the item is inaccessible from Workbench.
Import from the file system:
-
Click File > Import.
-
Click General > File System and then click Next.
-
Browse for the folder that contains the file to import.
Note:
If you import a file that is in a subfolder of
the folder you select, the subfolder is also created in the application.
-
Select entire folders or individual files to import.
You can select files from multiple folders.
-
Click the Browse button next to the Into Folder box and select
the application folder to contain the files.
To
see only the file types that you are interested in, click Filter
Types and select those file types.
-
To replace assets in the application that have the same name
and location as the items that you are importing, select Overwrite
Existing Resources Without Warning. If you do not select this option,
you decide whether to replace same-named files when they are being
imported.
-
Duplicate the folder structure of the file you are importing,
including all folders to the root of the file system. Select Create
Complete Folder Structure, and then click Finish.
Importing from LiveCycle ES archive files
To import items from LiveCycle ES archive files (that were
created using LiveCycle ES), first import the archive files into
LiveCycle ES2.5 using LiveCycle Administration Console. After importing,
the items in the LiveCycle ES archive file appear in the Processes,
Resources, and Events views as they did in the original LiveCycle ES
environment. For example, process versions appear in the same process
group in the Processes view.
Note:
If the root of the path of imported resources
is Applications, the imported resources do not appear in the Resources
view. For example, an LiveCycle ES archive file contains the resources
from the Application/LoanApplication folder. When this LiveCycle
ES archive file is imported, the contents do not appear in the Resources view.
Create applications before importing legacy items. (See
Adding and removing applications
.)
Legacy LCA files that include service configurations
In LiveCycle
ES, when processes used services that were configured using the Components
view, LiveCycle ES archive files included the service configuration. These
service configurations cause problems when they are imported into LiveCycle
ES2.5 environments. When you preview archive contents when importing
into LiveCycle ES2.5, deselect any service configurations for service components.
For
example, a LiveCycle ES process uses the LDAP service. The connection properties
for the LDAP service were configured using the Components view. When
the process is packaged in a LiveCycle ES archive, the archive includes
the service configuration. When imported, the service configuration
is appears as ServiceConfiguration_LDAPService in the preview. This
item should be deselected before importing into LiveCycle ES2.5.
Note:
Do not deselect service configurations for process
services.
Import legacy items from LiveCycle ES archive files:
-
Use LiveCycle Administration Console to import the LiveCycle
ES archive files. (See
Import and manage LiveCycle 8.x archives
in
LiveCycle ES2.5 Administration Help
.)
-
In Workbench, open the Processes view and refresh the view.
Refreshing causes any processes that were imported from the LCA
file to appear.
-
Open the Events view and refresh the view. Refreshing causes
any event types that were imported from the LCA file to appear.
-
Import the items that the LiveCycle ES archive file contained
from their run-time location. (See
Importing from the run-time environment
.)
Note:
Refresh
the Applications view to see the imported items.
|
|
|
|
|
