HTML Workspace in LiveCycle ES4

Adobe LiveCycle ES4 has come up with a brand new HTML based Workspace along with the traditional Flex-based Workspace. HTML Workspace matches the capabilities of the existing flex workspace and adds new capabilities to extend and integrate workspace and makes it more user-friendly. HTML Workspace is purely based on html technology and doesn’t require Adobe Flash player or Adobe Reader to work.

HTML Workspace is a web based application hosted on CRX. When Workspace is opened in a browser, a CRX resource is accessed, and the application is rendered as HTML page in the browser. Because it pure html based and even hosted on CRX, it becomes more easy to enhance and customize this workspace and takes no time in deploying new changes. This HTML Workspace has been designed into modular JavaScript components which can be individually customized and reused in other web applications.

htmlws_overview

Below are some key capabilities and new features of HTML Workspace:

  • Pure html JavaScript based application, even has the capabilities to take existing xdp or pdf and render it as complete html form. And hence increase its visibility from desktops to tablet devices.
  • HTML Workspace is the component-based software, so it can be easily customized and reused in other web applications. Each component follow Backbone library to have MVC architecture in web application.
  • HTML workspace supports a new summary pane for the tasks. With this summary pane, User can show additional information about the task using an external URL. This feature will be quite useful for a long running task where reviewers or approvers of the task can see the complete summary of the task instead of going through complete task form or other details.
  • HTML Workspace also support for managers view which will allow managers to access or act on tasks of their direct reports. It will also allow managers to drill down, in the Organization hierarchy, to tasks of their indirect reports.
  • One of the important features of HTML workspace is the support for integrating third-party applications inside HTML Workspace. This will allow Organizations to integrate their custom workflows into LiveCycle Workspace like render Adobe LiveCycle CM letter templates as tasks within LiveCycle Workspace window and thus complete the task in Workspace itself without going into LiveCycle CM UI.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 4.9/10 (11 votes cast)
Posted in Adobe LiveCycle ES4 | Tagged , , | 1 Comment

New PDF Export formats introduced in PDF Generator ES4

PDF Generator ES4 introduces new export formats which convert PDF documents to Office Open XML formats (DOCX, XLSX, and PPTX). These conversions use Acrobat based conversion route to perform the operation.
Similar to other existing export formats these new formats are only available on Windows platform, and are single-threaded. The output generated would have the same quality as standalone Acrobat Export option.
For converting files to the new formats the user can use the PDF Generator UI, and in Export PDF screen select the desired export format:

Export PDF Screen

Export PDF

For converting the files using Java API a developer can use the enumerations:

  • ConvertPDFFormatType.DOCX
  • ConvertPDFFormatType.XLSX
  • ConvertPDFFormatType.PPTX

Here is a sample code snippet for exporting to the new format:


//Create a ServiceClientFactory instance
ServiceClientFactory factory = ServiceClientFactory.createInstance(connectionProps);

//Create a GeneratePdfServiceClient object
GeneratePdfServiceClient pdfGenClient = new GeneratePdfServiceClient(factory);

//Get a PDF document to convert to an RTF document
String inputFileName = “C:\\testFile.pdf”;
FileInputStream fileInputStream = new FileInputStream(inputFileName);
Document inDoc = new Document(fileInputStream);

//Convert a PDF document to a DOCX document
ExportPDFResult result = pdfGenClient.exportPDF2(
inDoc,
inputFileName,
ConvertPDFFormatType.DOCX,
null);

//Get the newly created RTF document
Document createdDocument = result.getConvertedDocument();

//Save the RTF file
createdDocument.copyToFile(new File(“C:\\testFile.zip”));
}

As seen in the code above, the output generated is a zip file which contains the exported DOCX, XLSX or PPTX file.

 

For more information on the exciting new features introduced in Adobe LiveCycle ES4  refer to the LiveCycle ES4 documentation link: What’s new in Adobe LiveCycle ES4 .

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.5/10 (4 votes cast)
Posted in Adobe LiveCycle ES4, PDF Generator | Tagged , , | Comments Off

PDFG ES4 with UAC enabled

Adobe Livecyle ES3 SP2 and ES4 now supports running PDFG with UAC enabled. Apart from the code changes done in PDFG some OS level settings are also required. This article describes these settings and configurations required for PDFG to work seamlessly. However please note that UAC should be disabled at the time of Livecycle installation and Configuration.

 1) Update the following settings related UAC. From the Start-> run type gpedit.msc .Go to Windows Settings ->Security Settings-> Local Policies ->  Security Options

  • User Account Control:Only elevate executables that are signed and validated should be “Disabled”.

 snap1

2) Replace process level token should be turned On for the Administrators. Type gpedit.msc  Go to  Windows Settings ->Security Settings-> Local Policies -> User Rights management ->Replace Process level token.Add all the PDFG users here.
 snap2

 3) Change the folder permission of the PDFG temp folder and give rw access to all the users in step#2.

Additional Information:

  • PDFG temp should be created under c:\users\<UserName>\Appdata\Local\Temp\ pdfg-<Username>.Where Username is the user running the Appserver 
  • We need to explicitly give rw permissions for all users.Assigning permissions to admin group does not work.

P.S: If any of the setting is not done correctly you will see “Connection to failed service”.

 

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.0/10 (5 votes cast)
Posted in Adobe LiveCycle ES3, Adobe LiveCycle ES4, PDF Generator | Tagged , , | Comments Off

How to render xdp as HTML form in HTML Workspace

By default xdp forms are rendered as PDF forms even in HTML workspace. So to render/submit existing xdp/pdf as HTML form in HTML Workspace, we need to add a new action profile called “HTML” which will include render process as “render new html form” and submit process as “submit new html form”. Below are some simple steps to configure this:

1. Goto Adobe Livecycle Workbench ES4, and open your existing process for which you want to change the configuration regarding render/submit processes.

2. Then goto “Presentation & data” section in Process Properties window and click “manage action profiles” as depicted in below snapshot.

pic1

3. Then in “manage action profile” dialog, create another action profile and name it as “HTML”. With this profile, configure render process as “render new html form” and submit process as “submit new html form”. Select this profile to be used and click OK button to save your changes. See below snapshot.

pic2

Note: Please note change your action profile from default to html in all “assign task” or “start point” activity in this current process.

4. That’s it, now you can just check-in and deploy your updated process. Now if you open this process (start point) in HTML Workspace, it will be render/submit as HTML form.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.3/10 (4 votes cast)
Posted in Adobe LiveCycle ES4 | Tagged , , | Comments Off

Requirements and Recommendations for running LiveCycle PDF Generator ES4 on Windows 2008 server

To get the full advantage of PDF Generator features provided by LiveCycle ES4 on Windows 2008 Server, administrator needs to ensure that all the prerequisites are met for conversions to succeed. Based on the conversion formats required, some of these prerequisites may not be applicable.

This blog tries to list down these requirements with a brief description on each of them.

Run application server as a service

It is highly recommended that the LiveCycle server should be running as a Windows service. In case of turnkey installation, the service is created automatically as part of the installation, but for non-turnkey installations this needs to be done manually. Here are some helpful links (though the links may vary based on the specific version of the server you are on).

Select the user with which the application server should run

The user account used to run the application server needs to have following privileges:

  • User account should be Local System Account, or a member of the Local Administrators group on the machine
  • The user account should have ‘Replace a Process Level Token’ permission.

Local System account has this permission by default, but if the server is running with a user of Local Administrators group this permission needs to be granted explicitly. For granting this permission:

  1. In the Windows Start menu, click Run and then enter gpedit.msc.
  2. Click Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment and edit the ‘Replace a process level token’ policy to include the Administrators group.gpedit
  3. Add the user to the Replace a Process Level Token entry.

Note: In case of a cluster, the server needs to be run as an Administrator account to allow access to a shared GDS folder.

Disable UAC (User Account Control) during installation and LCM

It is required that User access control should be disabled on the server during the installation and LiveCycle configuration.

Steps to disable UAC on Windows Server 2008 R1

  1. To access the System Configuration Utility, go to Start > Run and then enter MSCONFIG.
  2. Click the Tools tab and scroll down and select Disable UAC.
  3. Click Launch to run the command in a new window.
  4. When finished, close the command window and close the System Configuration window.
  5.  Restart your computer.

Steps to disable UAC on Windows Server 2008 R2

  1. To access the System Configuration Utility, go to Start > Run and then enter MSCONFIG.
  2. Click the Tools tab and scroll down and select Change UAC Settings.
  3. Click Launch to run the command in a new window.
  4. Adjust the slider to the Never notify level.
  5. When finished, close the command window and close the System Configuration window.
  6. Restart your computer

Run PDF Generator configuration batch file

PDF Generator configuration batch file available at: <LiveCycle Installation Directory>\pdfg_config\Acrobat_for_PDFG_Configuration.bat needs to be executed on all the nodes in the cluster. In case of turnkey and non remote installations, this step is automatically performed on the server, but in case of remote deployment this step needs to be performed manually.

For details on running the configuration batch file on remote machines, please refer to the blog post: Configuring PDF Generator ES4 on windows for remote deployments.

Add users to PDF Generator user account list

PDF Generator requires atleast 1 user to be added to the PDFG User accounts list for conversions to work. This requirement is also enforced by the LiveCycle Configuration Manager (LCM). Here are some considerations while adding users to the PDFG user accounts list:

  • The users being added should have Administrative privileges on the server machines (part of Local Administrators Group)
  • In case of a cluster, these users should be valid on all the nodes in the cluster
  • If a new user is added, or an existing user is removed, a server restart is required
  • In case a user password is updated, the same needs to be updated in user account configuration in PDFG UI under User Accounts (password change does not require a server restart).

Ensure full read/write/modify permissions on LC temp / PDFG temp folder

By default all Local Administrator Group users have full control on all the folders (read/write/modify). But at times the domain controller enforces some additional security on the servers which can cause restrictions on certain folders.

Ensure that user with which application server is running, and all the user accounts added to PDFG users accounts list should have full control on the temp folder (configured during LCM run or through AdminUI >Home > Settings > Core System Settings > Configurations).

Permission issues may be seen when instead of adding the users individually, the Administrators group is given the permission. It is recommended that user accounts should be added individually.

Note: PDFG Temp folder refers to a folder inside the LC Temp folder, created on first PDFG conversion. PDFG temp folder is created with the name: pdfg-<username> when the server is running with an Administrator role user, or with the name: pdfg-<machinename>_ when running with Local System Account.

Granting permissions

  1. Right click on the temp folder
  2. Go to the Security tab
  3. Edit the permissions and add all the required users individually with Full control option.

Disable Windows error reporting

It is recommended that Windows error reporting should be disabled on the server machine to avoid third party dialogs during PDF conversions (as it can cause intermittent failures). To disable error reporting on the server:

  1. Open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.
  2. On the Server Manager home page, expand the Resources and Support area if it is not already open.
  3. Click Configure Windows Error Reporting.
  4. On the Windows Error Reporting Configuration dialog box, select ‘I don’t want to participate, and don’t ask me again’.

Set Adobe PDF Printer as the default printer

Various print route conversions require Adobe PDF printer to be set as the default printer. The printer is installed along with Acrobat installation and is required to be set as the default printer on the server machine.

To set the Adobe PDF printer as the default printer, right-click on the Adobe PDF printer and select ‘Set as default printer’

Note: If a remote desktop session is opened to the server machine and client has the option ‘use printers in the remote session’ enabled (default), the default printer on the server machine is modified and can result in failures. It should be ensured that the option is disabled while taking a remote desktop on the server machine.

Run System Readiness Tool (SRT)

System Readiness is run as part of LCM, and reports main configuration issues on the server. Based on the application/file types you plan to convert the report should not contain any errors/warnings. Some of the checks done by SRT include:

  • JAVA_HOME is set correctly, and is of supported version
  •  JAVA_HOME _32 is set correctly to a 32 bit JDK, and is of supported version
  • Acrobat_PATH is set correctly
  • Acrobat version is correct (Acrobat XI)
  • PDFGen.api is copied to Acrobat plugins folder
  • FrameMaker / PageMaker / OpenOffice / WordPerfect / Notepad path are set
  • Applications versions for various supported applications
  • Adobe PDF printer is set as the default printer
  • Print spooler is in a running state
  • PDFMaker DLL is registered

Verify file format specific requirements are met

For details on various application specific configuration please refer to the blog post: File Format specific PDFG configuration requirements in LiveCycle ES4.

 

For more information on the exciting new features introduced in Adobe LiveCycle ES4  refer to the LiveCycle ES4 documentation link: What’s new in Adobe LiveCycle ES4 .

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.3/10 (8 votes cast)
Posted in Adobe LiveCycle ES4, PDF Generator | Tagged , , , , | 1 Comment

Configuring PDF Generator ES4 on Windows for remote deployments

PDF Generator configuration batch file performs a set of configurations on the server machine which are required to successfully perform various conversions. The batch file is run as part of the LiveCycle configuration for turnkey and local deployments, but is required to be executed manually in case of remote deployments. For a clustered deployment, this needs to be run on all nodes in the cluster.

This post provides the steps to run PDFG configuration batch file manually on a remote Windows server machine.

Note: The configuration batch file needs to be run after the required software has been installed and initial dialogs dismissed (for Acrobat 11 and other required software based on the file formats you want to convert). A server restart is required in case you have already run LCM and the server is in a running state.

Steps to run the configuration batch file manually:

  1. Ensure UAC is turned off on the machine while performing this task.
  2. Log in to the remote LC server machine through which Acrobat XI was installed.
  3. Create a folder, eg: C:\LC_Config_Files
  4. From the machine where LiveCycle ES4 is installed – copy the following folders to the LC_Config_Files folder
    1. plugins
    2. pdfg_config
    3. pdfg_srt
  5. Create a folder with the name ‘configurationManager’ inside  LC_Config_Files folder
  6. On a command prompt
    1. Browse to the folder : LC_Config_Files\pdfg_config
    2. Run the batch file: Acrobat_for_PDFG_Configuration.bat
  7. Run SRT (System Readiness Tool) to verify the configuration. On a command prompt
    1. Browse to the folder : LC_Config_Files\pdfg_srt
    2. Run the command:  SystemReadinessTool.vbs out
    3. This will generate a report in LC_Config_Files\pdfg_srt\out (SystemReadinessTool.html)
    4. Review the generated report of any issues

For more information on the exciting new features introduced in Adobe LiveCycle ES4  refer to the LiveCycle ES4 documentation link: What’s new in Adobe LiveCycle ES4 .

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)
Posted in Adobe LiveCycle ES4, PDF Generator | Tagged , , , , | 1 Comment

File Format specific PDFG configuration requirements in LiveCycle ES4

PDF Generator supports a large number of file formats for conversion to PDF, and requires corresponding software installations on the server. Below is a list of applications which are supported by PDF Generator, including the file formats each application supports.

Generic Requirements:

  • PDF Generator is supported only on English, French, German and Japanese platforms (operating system), and each platform should have all  applications installed in the same language.
  • WordPerfect is only supported on English platform.
  • Some applications require environment variables to be defined.
  • Only 32 bit versions of applications below are supported.

Application specific requirements:

  • Adobe® Acrobat® XI Pro : XPS, DWG, DXF, DWF ,Image formats (BMP, GIF, JPEG, JPG, TIF, TIFF, PNG, JPF, JPX, JP2, J2K, J2C), HTML formats -
    • Acrobat_PATH should be set to Acrobat.exe  path
    • All initial registration/activation dialogs should be dismissed for all the PDFG user accounts configured on the server.
    • Acrobat should be installed after all Microsoft applications have installed.
    • Automatic updates should be disabled.

     

  • Microsoft Office, Microsoft Visio, Microsoft Publisher, Microsoft Project (versions: 2007/2010): DOC, DOCX,  XLS, XLSX, PPT, PPTX, RTF, TXT, VSD,PUB, MPP -
    • Acrobat_PATH should be set to Acrobat.exe  path
    • All initial registration/activation dialogs should be dismissed for all the PDFG user accounts configured on the server.
    • Acrobat plugin should be visible inside Word/Excel/PowerPoint/Visio/Project
    • Adobe PDF printer should be seen as default when printing
    • Adobe Acrobat Distiller should be launched manually once for all the PDFG user accounts configured on the server.

     

  • Adobe PageMaker® 7: PMD, PM6, P65, PM -
    • All initial registration/activation dialogs should be dismissed for all the PDFG user accounts configured on the server.
    • PageMaker_PATH should be set to PageMaker exe path

     

  • Adobe FrameMaker® 8.0: FM -
    • All initial registration/activation dialogs should be dismissed for all the PDFG user accounts configured on the server.
    • FrameMaker should be configured to use ‘Framemaker’ product interface (to be selected when FrameMaker is first installed). This can be updated from Preferences section too.
    • Adobe PDF printer should be seen as default when printing
    • FrameMaker_PATH should be set to FrameMaker exe path

     

  • Corel WordPerfect 12 / X4: WPD -
    • All initial registration/activation dialogs should be dismissed for all the PDFG user accounts configured on the server.
    • Adobe PDF printer should be seen as default when printing
    • WordPerfect_PATH should be set to WordPerfect exe path

     

  • OpenOffice 3.x: ODT, ODP, ODS, ODG, ODF, SXW, SXI, SXC, SXD, DOC, DOCX, XLS, XLSX, PPT, PPTX, RTF, TXT , Image Formats (BMP, GIF, JPEG, JPG, TIF, TIFF, PNG, JPF, JPX, JP2, J2K, J2C), HTML, HTM -
    • All initial registration activation dialogs should be dismissed for all the PDFG user accounts configured on the server.
    • OpenOffice_PATH should be set to OpenOffice installation directory

     

For more information on the exciting new features introduced in Adobe LiveCycle ES4  refer to the LiveCycle ES4 documentation link: What’s new in Adobe LiveCycle ES4 .

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.8/10 (4 votes cast)
Posted in Adobe LiveCycle ES4, PDF Generator | Tagged , , , , , , , , , , | 2 Comments

Optimizing Mobile Forms Performance

Optimizing Mobile Forms Performance

Livecycle ES4 Mobile Forms renders forms in the HTML5 format. The resultant output could be large depending on factors like the form size and images in the form. To optimize the data transfer, the recommended approach is to compress the HTML response using the Web Server from which the request is being served. This approach reduces the response size, network traffic, and the time required to stream data between the server and client machines.

This article describes the steps required to enable compression for the Apache Web Server 2.0 32 bit, with JBoss.

Note: The following instructions do not apply to servers other than the Apache Web Server, or to another version of the Apache Web Server. See documentation for that server.

Following steps demonstrates changes required to enable compression with Apache Web Server

Obtain the Apache web server software that is applicable to your operating system:

1)For Windows, download the Apache web server from the Apache HTTP Server Project site.

2)For Solaris 64 bit, download the Apache web server from the Sunfreeware for Solaris Website.

3)For Linux, the Apache web server is preinstalled on a Linux system.

Apache can communicate to JBoss using HTTP or AJP protocol. The following are configurations for optimization using HTTP.

1)Uncomment the following module configurations in APACHE_HOME/conf/httpd.conf  file

   LoadModule proxy_balancer_module modules/mod_proxy.so
   LoadModule proxy_balancer_module modules/mod_proxy_http.so
   LoadModule deflate_module modules/mod_deflate.so

 Note: For Linux, the default APACHE_HOME is /etc/httpd/

2)Configure the proxy on port 8080 of Jboss
Add following configuration in APACHE_HOME/conf/httpd.conf configuration file.

ProxyPass / http://<server_Name>:8080/
ProxyPassReverse / http://<server_Name>:8080/ 

3) Enable Compression

Add following configuration in APACHE_HOME/conf/httpd.conf configuration file.

 
<Location /lc/content/xfaforms>
  <IfModule mod_deflate.c>
     SetOutputFilter DEFLATE
     # Don’t compress
     SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-vary
     SetEnvIfNoCase Request_URI \.(?:exe|t?gz|zip|bz2|sit|rar)$ no-gzip dont-vary
    #Dealing with proxy servers
   
     <IfModule mod_headers.c>
        Header append Vary User-Agent
     </IfModule>
  </IfModule>
</Location>

4) To access the Livecycle server, use http://<machine_name>:80

Note: machine_name is the name of the server on which the Apache server is running.

Also see  What’s new in Adobe LiveCycle ES4 and Introduction to Mobile Forms.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 6.8/10 (4 votes cast)
Posted in Adobe LiveCycle ES3, Adobe LiveCycle ES4 | Tagged , , , , , , , , , , , , , , , , , | Comments Off

Adobe LiveCycle – Configuration Migration Utility

If you are a LiveCycle customer who manually sets configuration settings for LCAs and DSCs when duplicating an environment or migrating from one setup to another in your Dev, Staging or Production environment, then you may find this utility helpful. It exports the service configurations of all services deployed including LCAs in an XML which can then be imported on another setup to replicate these settings. If you like to be cautious and do settings manually, the XML output can serve as a good source for comparing the settings on the setups. One can also creates an HTML report using the output XML files, that will show the difference between service configurations of two LC system.

  • Export operation extract all the LiveCycle service configurations into an XML file.
  • Import operation takes this xml file as input and replicate the service configuration in the target system.
  • Diff operation generates an HTML report that compares the service configuration of two LC systems. To use this operation-
    1. Execute export operation on LC systems for which you want to take the difference
    2. Rename the xml file, generated as output of export operation, with host name.
    3. Execute bat/sh file after providing values to required field in ConfigurationMigrationUtility.properties file.
    4. This operation generates DiffReport.html file in the directory where the ConfigurationMigrationUtility.jar is placed, as output.

Usage instructions:

  1. Set JAVA_HOME environment variable if not already set.
  2. Set PATH environment variable for java if not already set.
  3. Copy and extract the attached ConfigurationMigrationUtility.rar file.
  4. Follow the instructions provided in readme.txt file placed in lib directory.
  5. Depending upon the operation you want to execute, provide information in the ConfigurationMigrationUtility.properties file.
    • operation – This can have value as either export, import or diff
    • server_url=This variable is for server url matching this pattern <http|https>://<Host_name|IP>:<port> e.g – http://localhost:8080

    • user_id=This variable will have your LiveCycle username

    • pass=This variable will have your LiveCycle password.

    • server_type=This variable must have value as either of JBoss, Weblogic or WebSphere

    • file=This variable will have the file path where the service configuration will be stored. This variable must have complete path for xml file. e.g – c:\tmp\service.xml
    • diffFile1= This is required only for diff operation. This variable will have the path of first xml file used for diff operation.
    • diffFile2=This is required only for diff operation. This variable will have the path of second xml file used for diff operation
  6. Execute bat/sh file.

 

Note:

  1. lib directory and ConfigurationMigrationUtility.jar must be placed in same directory.
  2. ConfigurationMigrationUtility.properties file must be placed in the same directory as ConfigurationMigrationUtility.jar else provide its complete path in the bat/sh file.

Disclaimer:This is not an Adobe officially provided utility. This is designed just to help customers. Please test it in QE environment once before using it in production.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.3/10 (6 votes cast)
Posted in Adobe LiveCycle ES3 | 4 Comments

LiveCycle ES4 – Routing Log Messages

While working with any application server, changing the log level on the fly is always a hectic task. But CQ embedded in Adobe LiveCycle ES4 offers a feature that simplifies adding new loggers or changing the log level for any component of LiveCycle ES4.

Following are the steps to change the log level in Adobe LiveCycle ES4

  1. Login to Felix web console using “http://host-name:port/lc/system/console/configMgr”. Change the host-name and port with your app server host name and port number.
  2. Now search and click on “Adobe LiveCycle Embedded Mode Configuration”, check in the check box named as “Route log message” and click save button. This will enable the routing of log message through Sling Logging layer.Embedded_Mode_Configuration
  3. Now Search “Apache Sling Logging Logger Configuration” and click on “+” button on right hand side of this tab. Apache_Sling_Logging_Logger_Configuration
  4. A new window will pop up. Provide required information in this window –
    • Log Level – To specify the log level you want for that particular component.
    • Log File – Specify the path for the log file in this field.

    • Message Pattern – Specify the log pattern in this field.
    • Logger – Specify the package of the component for which you want to change the log level. e.g. to add the logger for authentication manager give logger name as com.adobe.idp.um

    Configuration_window
    To add logs of more than one component in the same file, simply click the “+” button at end of logger field and provide the package name of the component for which you have to add the logs in the new logger field.

  5. After filling all the required fields click save. Now all the logs for the particular component, meeting the log level, will be added in the log file mentioned in the above steps.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.8/10 (5 votes cast)
Posted in Adobe LiveCycle ES3 | 1 Comment