Note:
Press
F1
in Configuration Manager to view Help
information for the screen you are viewing. You can view the configuration
progress at any time by clicking View Progress Log.
Note:
During configuration, if you must reset the data in Configuration
Manager by using the Reset to Default option, ensure that you relaunch
the Configuration Manager. Otherwise, you may encounter some missing
configuration screens.
If you are continuing from the AEM forms on JEE installation,
proceed to step 3; otherwise, navigate to the
[aem-forms root]\
configurationManager\bin folder
and run
ConfigurationManager.bat
.
When prompted, select the language to use, and then click
OK
.
On the Welcome to Adobe Experience Manager forms screen,
click
Next
.
On
the Upgrade Task Selection screen, ensure that
Upgrade from LiveCycle ES4 SP1
is
deselected. Click
Next
.
On
the Turnkey Mode screen, select
Custom Mode
and click
Next
to
proceed to the next section. Custom Mode allows you to customize
system configurations.
4.3.2.2 Selecting modules
On the Modules screen, ensure that the LiveCycle
ES4 modules you want to upgrade are selected. By default, all the
modules that you select will be licensed with an Evaluation License.
Click
Next
.
Note:
Some modules have technical
dependencies on other modules for proper configuration and functioning.
Configuration Manager displays a dialog and does not allow to proceed
further if mutually dependent modules are not selected. For example,
you must select Forms, Output, and Content Repository modules if you
are configuring Correspondence Management.
4.3.2.3 Selecting Tasks
On the Task Selection screen, ensure that all
the required tasks are selected, and then click
Next.
Note:
The
Configure Application Server
and
Validate Application Server Configuration
tasks are not available for selection for JBoss turnkey. The JBoss turnkey method does not support these tasks because the application server is already configured for AEM forms on JEE.
4.3.2.4 Configuring EAR, Fonts, and GDS
On the Configure Adobe Experience Manager
forms (1 of 5) screen, click
Configure
and, when the EAR
files have been configured, click
Next
. Depending on the
number of modules that are included in the configuration, this process
may take several minutes to complete.
On the Configure Adobe Experience Manager forms (2 of 5)
screen, set the directories that AEM forms on JEE will use to access
fonts and then click
Next.
Click
Edit configuration
to
change any values on this screen. This button is not available when
the Configuration Manager is run for the first time, but is available
on the second and subsequent runs of the Configuration Manager.
(Optional) To change the default location of the
Adobe server fonts directory
,
type the path or browse to the directory. The default path is [aem-forms
root]/fonts
To change the default location of the
Customer fonts directory,
click
Browse
or
specify a new location for your customer fonts.
Note:
Your
right to use fonts provided by parties other than Adobe is governed by
the license agreements provided to you by such parties with those
fonts, and is not covered under your license to use Adobe software.
Adobe recommends that you review and ensure that you are in compliance
with all applicable non-Adobe license agreements before using non-Adobe
fonts with Adobe software, particularly with respect to use of fonts
in a server environment.
(Optional) To change the default location of the
System fonts directory
, type
the path or browse to the directory.
(Optional) To enable FIPS, ensure that Enable
FIPS
is
selected. Select this option only if you require the Federal Information
Processing Standards (FIPS) to be enforced.
On the Configure Adobe Experience Manager forms (3 of 5)
screen, accept the default location for the
Location of temporary directory
,
or enter the path or click
Browse
to specify the path. The
default location is
[aem-forms root]/temp
. Click
Next
to
continue.
On
the Configure Adobe Experience Manager forms (4 of 5) screen, accept
the default location for the
Global document storage directory path
,
or click
Browse
to specify the fully qualified path. Click
Next
to
continue.
The default location is
[aem-forms root]/gds
.
On the Configure Persistent Document Storage (5 of 5) screen,
select either
Use GDS
or
Use database
, and then
click
Configure
.
Use GDS
:
Use the file system based GDS for all persistent document storage.
This option provides the best performance and a single location
for GDS.
Use database
: Use the database for AEM forms on JEE
for storing persistent documents and long-lived artifacts. However,
the file-system based GDS is also required. Using the database simplifies
backup and restore procedures.
Click
Next
.
4.3.2.5 Configuring Acrobat for PDF Generator
(PDF Generator only)
On the Configure Acrobat
For PDF Generator screen, click
Configure
to run the configuration
script. When complete, click
Next
.
On the Configure Adobe Experience Manager forms Summary screen,
click
Next
.
4.3.2.6 Configure CRX
The CRX Configuration screen allows you to configure
the CRX repository and install it into the adobe-livecycle-cq-author.ear
EAR file.
Specify the path to the repository.
The default location is
[aem-forms root]
/crx-repository.
Note:
Ensure
that the CRX repository path does not contain spaces and the content
repository is available on all the nodes of the cluster. After the
configuration is complete, copy the content repository from local
node to all the nodes on the same location (as specified on the
CRX configuration screen) .
Select the repository type, as appropriate and keep a note
of the following points:
CRX3 TAR is not supported
in clustered deployments.
If selecting CRX3 Mongo DB, specify the Mongo database name
and URL to the database. The format of the URL is:
mongodb://<HOST>:<Port>
.
HOST:
IP address of the machine running MongoDB.
Port: Port number
used for the MongoDB. The default port number is 27017.
CRX3 RDB is supported only with Oracle 12c or IBM DB2 10.5
databases. Selecting this option sets the CRX repository persistence
to RDB MK (document MK) .
Optionally, select AEM Samples need to be installed to install
AEM samples.
Click
Configure
to create the required repository
files at the specified location.
Note:
If your AEM
forms on JEE server is running remotely, select
Server is running on remote host
,
and specify the path to the repository on the remote host.
Note:
Clustered
environments with relational databases are now supported for production
use under a "gated" program. If you intend to use a relational database in
a clustered environment, contact AEM Forms product team at forms_documents@adobe.com
for approval. Also ensure that the mandatory patches are
installed and configured.
Click
Next
to continue.
Note:
Once
the packages are configured, you cannot remove them by re-running the
Configuration Manager. For clean uninstallation of deployed packages,
you need to uninstall and delete the packages using Package Manager.
4.3.2.7 Configuring turnkey JBoss SSL
On the Configure Turnkey JBoss SSL screen, add
the information to configure the SSL certificate and click
Configure JBoss SSL
,
when complete click
Next
.
You can skip this step by
selecting the Skip Configuration and configure it later using Configuration
Manager.
Certificate Alias:
The alternate
unique name that is used to reference the certificate.
Keystore filename:
The name of the keystore that is
assigned to store the keys and the certificate.
4.3.2.8 Install verification samples
(
Forms, Assembler, and Output, only
) On
the Adobe Experience Manager forms Installation Verification Sample
(IVS) EAR files screen, you can install three service-specific sample
applications. Select
Include IVS EARs in deployment set
and
click
Next
to install these sample files.
adobe-output-ivs-jboss.ear, adobe-assembler-ivs.ear,
and
adobe-forms-ivs-jboss.ear
appear
only if you have selected respective modules on the Modules screen.
Note:
Do not deploy the IVS EAR files to a production
environment.
4.3.2.9 Deploying AEM forms EARs
On the Deploy AEM forms EAR files screen, select
the EAR files you want to deploy to JBoss, click
Deploy
and
when complete, click
Next
.
Note:
During EAR
files Deployment to AEM forms on JEE, certain errors may be displayed
regarding EARs being unable to locate the correct table. You may
ignore these errors.
4.3.2.10 AEM forms Database Initialization
On the Adobe Experience Manager forms Database
Initialization screen, verify the host and port information, and
then click
Initialize
. The database initialization task creates
tables in the database, adds default data to the tables, and creates
basic roles in the database. When the initialization completes successfully,
and then click
Next
.
Do not skip
this step. Database initialization does not harm legacy data.
4.3.2.11 Server Information
On the Adobe Experience
Manager forms information screen, type the User ID and password
for AEM forms on JEE, and click
Verify Server Connection
.
When the validation is complete, click
Next
.
Important:
By default, the AEM forms
on JEE User ID is
administrator
and the password
is
password
. After completing the initial configuration,
change the default password in administration console.
The server information that appears on this screen represents
default values for the deployment. Verifying the server connection
helps narrow troubleshooting in case failures occur in the deployment
or validation. If the connection test passes but deployment or validation
fails in the next few steps, connectivity issues can be eliminated
from the troubleshooting process.
4.3.2.12 Central Migration Bridge Service Deployment Configuration
On Central Migration Bridge Service Deployment
Configuration screen, select
Include Central Migration bridge service in deployment
if
you are licensed to configure AEM forms on JEE with Central Pro
or Web Output Pak, and click
Next.
4.3.2.13 AEM forms Components Deployment
On the Adobe Experience Manager forms Component
Deployment screen, click
Deploy
. The components deployed
at this time are Java archive files that plug into the service container
for AEM forms on JEE for the purposes of deploying, orchestrating,
and executing services. When the deployment has completed successfully,
click
Next
.
On the Adobe Experience Manager forms Component Deployment
Validation screen, click
Validate
. Configuration Manager
validates that the Java archive files are deployed to and running
on the J2EE server for AEM forms. When the validation is completed
successfully, click
Next
.
4.3.2.14 Configuring AEM forms Components
On the Configure Adobe Experience Manager forms
Components screen, select the AEM forms on JEE modules to configure,
and then click
Next.
The screens that appear next depend
on your selections on this screen.
4.3.2.14.1 Configure Connector for EMC Documentum
On the Specify Client for EMC Documentum
screen, do one of the following tasks:
Deselect the
Configure Connector for EMC Documentum Content Server
option
to manually configure EMC Documentum later, and then click
Next
.
Leave the
Configure Connector for EMC Documentum Content Server
option
selected, enter the appropriate version and directory path for EMC Documentum
client, and click
Verify
. When complete, click
Next
and complete
the tasks on the following screens:
On the Specify
EMC Documentum Content Server Settings screen, specify the required
values and click
Next.
On the Configure Connector for EMC Documentum screen, click
Configure Documentum Connector
.
When complete, click
Next.
4.3.2.14.2 Configure Connector for IBM Content Manager
On the Specify Client for IBM Content Manager screen,
do one of the following tasks:
Deselect the
Configure Connector for IBM Content Manager
option
to manually configure IBM Content Manager later, and then click
Next.
Leave the Configure Connector for IBM Content Manager option
selected, enter the appropriate directory path for IBM Content Manager
client, and click
Verify.
When complete, click
Next
and
complete the tasks on the following screens:
On the
Specify IBM Content Manager Server Settings screen, specify the required
values and click
Next.
On the Configure Connector for IBM Content Manager screen,
click
Configure IBM Content Manager Connector.
When complete,
click
Next.
4.3.2.14.3 Configure Connector for IBM FileNet
On the Specify Client for IBM FileNet screen,
do one of the following tasks:
Deselect the
Configure Connector for IBM FileNet Content Manager
option
to manually configure IBM FileNet later, and then click
Next.
Leave the Configure Connector for IBM FileNet Content Manager
option selected, enter the appropriate version and directory path
for IBM Filenet client, and click
Verify
. When complete,
click
Next
and complete the following screens:
On the Specify IBM FileNet Content Server Settings screen,
specify the required values and then click
Next.
On the Configure Connector for IBM FileNet Process Engine
screen, specify the appropriate version (if enabled) and directory
path, and then click
Verify.
When complete, click
Next
.
On the Specify IBM FileNet Process Engine Server Settings
screen, specify the required values and click
Next.
On the Configure Connector for IBM FileNet screen, click
Configure FileNet Connector.
When
complete, click
Next.
4.3.2.14.4 Configure Connector for Microsoft SharePoint
On the Configure Adobe Experience Manager forms
Connector for Microsoft SharePoint screen, do one of the following
tasks:
Deselect the
Configure AEM forms Connector for Microsoft SharePoint
option
to manually configure Microsoft Sharepoint later, and then click
Next.
Leave the
Configure AEM forms Connector for Microsoft SharePoint
option
selected. Specify the required values, and click Configure SharePoint Connector.
When complete, click
Next
.
4.3.2.14.5 Verifying Configuration for ECM Connectors
On the Verify Configurations screen, do one
of the following tasks:
If you are configuring the
connectors for the first time or have modified any of the configurations
on the previous screens, leave the
Restart Application Server
option
selected and click
Validate Configuration
s
. When successfully
validated, click
Next
.
Note:
The validation of IBM FIleNet
may fail if there are special characters, such as hyphen (-), underscore
(_), comma (,), or dot (.) in the directory name containing the
IBM FileNet client.
If you wish to configure connectors later, deselect the
Restart Application Server
option
and click
Validate Configurations
. When successfully validated,
click
Next
.
4.3.2.14.6 Configuring PDF Generator
In the
Admin user credentials for native PDF conversions
screen,
specify the user name and password of a user with administrative
privileges on the server machine. Click
Add user.
Add
at least one administrative user for Windows 2008 Server and Click
Next
.
Note:
On Windows 2008 Server, disable User Account Control
(UAC) for the users you add. To disable UAC, click
Control Panel > User Accounts > Turn User Account Control on or off
and
deselect
Use User Account Control (UAC) to help protect your computer
.
Click
OK
. Your changes become effective when the system is restarted.
In the Document Services PDF Generator System Readiness Test
screen, click
Start
to validate if the system has been configured
correctly for PDF Generator. Review the System Readiness Tool Report
and click
Next
.
4.3.2.14.7 Configuring Acrobat Reader DC extensions Credential
On the Acrobat Reader DC extensions Credential
Configuration screen, specify the details that are associated with
the Reader Extensions credential that activates the module services.
Note:
You
can skip this step at this time by selecting
Configure later using AEM forms administration console
.
You can configure the Acrobat Reader DC extensions credential by
using administration console after you complete the deployment.
(After logging in to administration console, click
Home
>
Settings
>
Trust Store Management
>
Local Credentials
.)
Click
Configure
and
then click
Next
.
4.3.2.15 Task summary
Review the Configuration Manager task summary list and
select
Next Steps
to launch an html page containing information
about user and administrative interfaces for AEM forms on JEE. Click
Finish
.
Note:
You
will see a message on the screen to restart the server. However,
do not immediately restart. Ensure that error.log is stable and
all bundles (except signatures) are in active mode before you restart
the server.