1. 3. Once installation done, log on with administration console with http://localhost:8080/adminui. The default user/password : administrator/password.
For security reasons please change default password immediately.
If you can see the following screen, it means your installation is successful.
If you encounter any errors please check the installation logs. The path is:
"C:\Adobe\Adobe LiveCycle ES4\Adobe_LiveCycle_ES4_InstallLog.log" in my laptop.
1. 4. Configure JBoss server as a service in OS. You can find how to do this in document in path "C:\Adobe\Adobe LiveCycle ES4\jboss\bin\README-service.txt". If you are installing the trial version on your laptop, it is recommended to set the service startup type as “Manual”. Or else every morning when you launch your laptop, you must have a cup of coffee because you can really use it.
1. 5. Do some health check on server. Click home->services->LiveCycle PDF Generator ES4:
Click “Create PDF”:
Load any document with type other than PDF to try:
You may meet with following error messages:
1.
In fact the JBoss server uses Adobe Acrobat XI Pro to convert the document into PDF format.
The error message prompts you that either Acrobat XI Pro is not installed or there is something wrong with environment variable set up. Don’t mix Acrobat XI Pro with Acrobat Reader XI!
Acrobat has far more powerful functionalities than the latter:
You can also download Acrobat XI Pro trial version from here:
Install and maintain the environment variable:
1. 6. Import the docb_assmwml.lca attached in the note.
In admin console Home->Services->Applications and Services, ensure the status of docb_assemwml is running:
1. 7. Create the consumer proxy class in ABAP system as usual. Implement the BAdI by copying the code from note attachment. The code could not be directly activated since the generated data proxy used in the code does not exist in your own system. You must manually replace them with your own data proxy.
1. 8. Test the application.
The request variable ls_invoke_request contains the binary content of original document in docx format, the response variable contains the converted binary content of PDF format, if successful. In case the conversion fails, you can again check the server.log to find root cause. Alternatively you can also use tcode SRT_UTIL to check.
ICM_HTTP_CONNECTION_FAILED: please firstly check whether your server is available, secondly check whether your RFC destination to server works or not:
ICM_HTTP_TIMEOUT: this error occurs occasionally in my testing since I install the server in my laptop and it took the server a huge time to try to convert a complex docx file into PDF format. If you also meet with this error, try to enlarge the time out threshold setting in admin console.
HTTP Code: 500 ( Internal Server Error 😞 it indicates some exception raised from server side when doing the conversion job.
For example: the below detail explanation gives you a hint that the environment for Acrobat XI pro is not set properly.
And this error information demonstrates that the requested service “docb_assemwml” could not be found in server side. Either check in server side whether the status of it is running or check the name of service is correct.
If everything runs well you will see final PDF displayed.
You can also save the file locally and open it with any PDF reader. If the PDF is converted via trial version of Adobe Livecycle ES, you will see the corresponding water mark on it.
Summary: if you reach here I really appreciate your reading on this blog. Adobe LC ES has far more powerful functionalities and the feature in this blog is just a tip of iceberg. You can explore more in Adobe website. My team is responsible for Document builder in SAP. If you have any questions regarding it, just feel free to contact me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |