Posts tagged "developer"

How to obtain EchoSign developer API key

One of the key features of AEM 6.0 Forms is integration with EchoSign service. Any XFA based adaptive form can be configured to be digitally signed using EchoSign service.

During development time you may want create an XFA based adaptive form to see the end-to-end signing workflow. For that one of the pre-requisites is to have an EchoSign API key. You may want to obtain a developer key during development phase before going to production.

I am listing down the steps to obtain an EchoSign Developer API key

  1. Register yourself as an EchoSign developer by filling up this simple form , select the checkbox if you agree to Terms of Use and privacy policy and Click Create my account
  2. You will receive an automated registration email from EchoSign to your registered email account, check your Inbox (spam folder if necessary) and activate the account by clicking the URL provided in the mail
  3. Log on to EchoSign
  4. Navigate to “Account tab” and click “EchoSign API” panel on left hand side tabbed panel items
  5. Copy the API key which needs to be provided when creating a cloud service configuration for EchoSign service in AEM 6.0
  6. The below image shows where to look for API key when logged on to EchoSign

 

EchoSign API Key

EchoSign

 

 

–Santosh

http://about.me/nskumar

Quick and Easy steps to run Author & Publish Systems of Correspondence Management ES4

Steps to setup Correspondence Management system with author and publish instances configured

It’s recommended to perform these steps on your development system where you would like to  have a setup in less amount of time to get started with the application

For stage, UA or prod systems please follow the detailed install & config guides

 

  1. Run LiveCycle installer and complete installation , before running LCM follow as mentioned in next step
  2. Go to <LC_Root_Directory>/jboss/server , create a copy of lc_turnkey under the same folder but with different name .. say lc_publish_turnkey (Publish instance needs a separate JBoss profile so this new profile can be used for publish instance)
  3. Now run LCM and complete the configuration manager – After completing LCM run You will have Author instance of CM up and running , now you need to perform few more steps to have author and publish running on same machine and configured to talk to each other
  4. LCM creates a folder with name crx-repository under <LC_Home_Directory> which is used as a repository for author instance
  5. Create a new folder under <LC_Home_Directory> with name “crx-publish-repository” (without quotes) , Go to <LC_Home_Directory>\configurationManager\export\crx-quickstart and copy install folder along with it’s contents and paste it under <LC_Home_Directory>\crx-publish-repository such that the contents under publish repository would appear like this after pasting the contents <LC_Home_Directory>\crx-publish-repository\install\
  6. Go to <LC_Home_Directory>\configurationManager\export Copy adobe-livecycle-cq-publish.ear file and paste it in <LC_Home_Directory>\jboss\server\lc_publish_turnkey\deploy folder
  7. Start lc_publish_turnkey profile from command prompt using command as “run -c lc_publish_turnkey -Dcom.adobe.livecycle.crx.home=”C:/pathToLCHomeDirectory/crx-publish-repository” -Djboss.service.binding.set=ports-01 -b 0.0.0.0” [o is zero in case you try to copy paste this content]
  8. For the first time start up of publish instance , It takes around ten minutes to completely start as it unpacks packages and creates repository , When the server is up and running You can use following URLs to log on to author and publish systems
  9. Author Manage Assets UI – http://hostname:8080/lc/cm , Publish Manage Assets UI – http://hostname:8180/lc/cm (You can login as default super admin i.e administrator/password – Change the password if needed)
  10. One last setting before you are done – Go to http://authorinstancehostname:8080/lc/etc/replication/agents.author/publish.html  , Login as admin\admin , Click Edit , Go to Transport tab and modify URL to http://localhost:8180/lc/bin/receive?sling:authRequestLogin=1 , Click OK , Click Test Connection and ensure that you see success message

Now you have running Correspondence Management system with author instance running on port 8080 and publish instance running on port 8180

 

Santosh