5.1.1 Perform a system image backupAfter LiveCycle is installed and deployed into production
areas and before the system is live, it is recommended that you
perform a system image backup of the servers on which LiveCycle
is implemented. Also take backup of CRX repository.
The
LiveCycle database, GDS directory, and application servers must
be part of this backup. This is a complete system backup that you
can use to restore the contents of your computer if your hard drive
or entire computer stops working. See the LiveCycle
Backup and Recovery topic in Administration Help .
5.1.2 Restart the application serverWhen you first deploy LiveCycle, the server is in a deployment
mode in which most modules are in memory. As a result, the memory
consumption is high and the server is not in a typical production
state. You must restart the application server to get the server
back into a clean state.
5.1.3 Verify the deploymentYou can verify the deployment by logging in to Administration
Console. If you log in successfully, then LiveCycle is running on
the application server and the default user is created in the database.
To verify the CRX repository deployment, access the CRX welcome
page.
You can review the application server log files to ensure that
components were deployed correctly or to determine the cause of
any deployment issues you may encounter.
5.1.3.1 Accessing LiveCycle Administration Console Administration Console is the web-based portal for accessing
a variety of configuration pages where you can set run-time properties
that control the way LiveCycle operates. When you log in to Administration
Console, you can access User Management, Watched Folder, and Email
client configuration, and administrative configuration options for
other services. Administration Console also provides access to Applications
and Services, which administrators use for managing archives and
deploying services to a production environment.
The default user name and password for logging in is administrator and password.
After you log in the first time, access User Management and change the
password.
Before you access Administration Console, LiveCycle must be deployed
and running on your application server.
For information about using Administration Console, see Administration Help.
Type the following URL in a web browser:
http://[hostname]:[port]/adminui
For
example: http://localhost:8001/adminui
Note: The
default port number for WebLogic Server is 7001. When you created
a new managed server, you may have set a different port. Managed
server uses a default port of 8001.
If you have upgraded to LiveCycle, enter the same administrator
user name and password as that of your previous LiveCycle installation.
In case of a fresh installation, enter the default user name and
password.
After you log in, click Services to access the service
administration pages or click Settings to access the pages
on which you can administer settings for different modules.
5.1.3.2 Change the default password of LiveCycle AdministratorLiveCycle creates one or more default users during the
installation. The password for these users is in the product documentation
and is publicly available. You must change this default password,
depending on your security requirements.
The LiveCycle administrator user password is set to “password”
by default. You must change it in Administration Console > Settings
> User Management.
Also, it is recommended to change the default password for CRX
Administrator.
For detailed information, see Change
the default administrator password.
5.1.3.3 Accessing CQ Welcome PageCQ welcome page is the web-based portal for accessing various
CQ components, administration, deployment and development tools.
The default user name and password for logging in is administrator
and password (same as LiveCycle Administrator).
Access the welcome page using the following steps:
Type the following URL in a web browser:
http://[hostname]:[port]/lc/welcome
Enter the same administrator user name and password as mentioned
above.
After you log in, you can access various components, administration, deployment
and development UIs.
5.1.3.4 Accessing OSGi Management ConsoleIn CQ, components are in form of OSGi bundles which are
deployed to Apache Felix OSGi container. OSGi console provides a
way to manage OSGi bundles and services configurations. The default
user name and password for logging in is admin and admin (same as
CRX Administrator).
Access the OSGi Management console using the following steps:
Type the following URL in a web browser:
http://[hostname]:[port]/lc/system/console
Enter the same administrator username and password as mentioned
above.
After you log in, you can access various components, services,
bundles and other configurations.
5.1.3.5 Change CQ Administrator default passwordCQ embedded within LiveCycle has two administrator users
as mentioned below.
Super Administrator (administrator): The Super
Administrator user can access various CQ/CRX UIs and perform admin
operations. The default username and password are same as LiveCycle
Administrator, administrator/password. This user doesn't
have access to OSGi Management Console. The default password of
this user can be changed using LiveCycle Administrator console only
as mentioned in section Change default LiveCycle password.
The changed password will be applicable for both LiveCycle and CQ.
Administrator (admin): This user can access to OSGi console
in addition to CQ/CRX UIs and has administrator privileges. The
default username and password for the user are admin/admin.
To change the default password follow the below mentioned steps:
Type the following URL in a web browser.
http://[hostname]:[port]/lc/libs/granite/security/content/admin.html
Login using following credential:
Username:
admin
Password: admin.
Search for user Administrator.
Click on the user in left pane, the user details is displayed
in the right pane.
Click on Edit icon in the right pane.
On the edit page in the right pane, provide new password
in the New Password field and current password in Your Password field.
Click Save icon in the right pane.
Re-login using the changed password to verify.
5.1.3.6 View the log filesEvents, such as run-time or startup errors, are recorded
to the application server log files. If you have problems deploying
to the application server, you can use the log files to help you
find the problem. You can open the log files by using any text editor.
Log
files are located at [appserverdomain]/servers/[managed server name]/logs
directory:
Following CRX log files are located at [ CRX_home]/ error.log
audit.log
access.log
request.log
update.log
|
|
|