ADS configuration and ADS programming

Hi Everyone:
Would you like to give me some hints to solve the following problems?
Two question here :
1. How to configurate a J2EE engine after you install ADS plugins? I have followed the guide of Scott Jones. <a href="/people/scott.jones/blog/2007/09/13/installing-and-configuring-sap-interactive-forms-by-adobe-for-the-sap-netweaver-composition-environment:///people/scott.jones/blog/2007/09/13/installing-and-configuring-sap-interactive-forms-by-adobe-for-the-sap-netweaver-composition-environment But when I run non-interaction form demo on my J2EE engine, the complier give error prompt :"http://ctud50055576a:50200/inspection.wsil/" can't be recogonized. in IE,I have checked the address of "http://ctud50055576a:50200/inspection.wsil/" , which is definitely the address of wsil. all of segements are correct.
2. where I can find the package of class WDPDFObjectFactory? I mean the according SDA in the client plugins package.
Thanks a lot, I'm almost exhausted by these two problems.

Thanks for SBS's credential file.
I have already add this license into my local J2ee engine.
But when running the demo <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/webdynpro?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#48">Dynamic Non-Interactive PDF Forms</a>, I still meet with such problem :
Caused by: com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (302) Found. The requested URL was:"http://ctud50055576a:50200/inspection.wsil, used user to connect: ADSUser"
     at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getEndpointConfigurations(DestinationsHelperImpl.java:933)
     at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getWSDLUrl(DestinationsHelperImpl.java:401)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.getWSDLUrl(GenericServiceFactory.java:222)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:192)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:175)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:160)
     at com.sap.tc.adobe.pdfobject.core.PDFObjectDII.invoke(PDFObjectDII.java:278)
     ... 68 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (302) Found. The requested URL was:"http://ctud50055576a:50200/inspection.wsil, used user to connect: ADSUser"
     at com.sap.esi.esp.service.server.query.discovery.WSTransportSettingsResolver.resolveEntity(WSTransportSettingsResolver.java:362)
     at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.initialize(WSQueryImpl.java:281)
     at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSEndpoints(WSQueryImpl.java:165)
     at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getEndpointConfigurations(DestinationsHelperImpl.java:924)
     ... 74 more
It seems something related with Destination configuration.
Exactly following the guide of  Setting Up Basic Authentication in a Java Environment of ""<a href="http://help.sap.com/saphelp_nwce10/helpdata/en/37/504b8cbc2848a494facfdc09a359b1/frameset.htm">ADS configuration guide for SAP Netweaver 7.1 SP3</a>
In this document, in deployable Proxy class "DestinationSi", We need to add one logicport named after "Configport_Document".
And the WS endpoint is http://<host>:<port>/inspection.wsil
I suspect if such point is right or not, because the Web service of ADS web service address is different from such address, in WSnavigator, I find the according address is :
http://<host>:<port>//AdobeDocumentServices/Config?wsdl&style=document&mode=standard
So did a trial to use this Endpoint and filled in "DestinationSi" proxy class, but the server still refused to run the interactive form correctly, give error like this :
Caused by: com.sap.engine.services.webservices.espbase.query.exceptions.TechnicalException: Deserializing WSDL stream http://ctud50055576a.ctul.sap.corp:50200/AdobeDocumentServices/Config failed
     at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.getWSDLDefinitions(WSQueryImpl.java:509)
     at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.initialize(WSQueryImpl.java:310)
     at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSEndpoints(WSQueryImpl.java:165)
     at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getEndpointConfigurations(DestinationsHelperImpl.java:924)
     ... 74 more
Caused by: com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: Invalid Response Code: (404) Not Found. The request URL was:"http://ctud50055576a.ctul.sap.corp:50200/AdobeDocumentServices/Config, used user to connect: ADSUser". Check, whether the URL is correct, and the Web Service that you are requesting is up and running.
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:140)
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)
     at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.getWSDLDefinitions(WSQueryImpl.java:507)
     ... 77 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found. The request URL was:"http://ctud50055576a.ctul.sap.corp:50200/AdobeDocumentServices/Config, used user to connect: ADSUser". Check, whether the URL is correct, and the Web Service that you are requesting is up and running.
     at com.sap.esi.esp.service.server.query.discovery.WSTransportSettingsResolver.resolveEntity(WSTransportSettingsResolver.java:362)
     at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:127)
     ... 80 more
Feel confused for such strange problem.
SBS, would you like to give me some hints for it?
Message was edited by:
        Orlando Ding

Similar Messages

  • ADS Configuration Issue : ADS Call Failed

    Hi All,
    We are trying to implement the ADS Configuration Newly in our Development Portal 7.0.
    We have done all the configuration steps as per the standard ADS configuration Document.
    When we try to execute the Connection Test HTTP Destination ADS RFC Connection test in backend we are getting 302 Found return code in R3.
    We also tried trouble shoot as per the NOTE 944221... The follwoing test results are as follwos :
    => FP_PDF_TEST_00 By selecting the ADS connection the result is succesfull. - OK
    => FP_TEST_00 By selecting ADS Connection and tried to execute we got error - ERROR
         Error : ADS: com.adobe.ProcessingException: com.adobe.Processing(200101)
    => FP_CHECK_DESTINATION_SERVICE by selecting the ADS connecting and executed,
          without destination it is success - OK
          and with destination it is failing - ERROR
         Error : SYSTEM ERROR : com.adobe.ProcessingException: com.adobe.ProcessingException: Problem accessing the data from Destination: dest:FP_ICF_DATA_X45//sap/bc/fp/form/layout/FP_FORM_SECURITY_TEST.XDP?fp-lang..
    => FP_TEST_IA_01 is also failing - ERROR
         Error : ADS: com.adobe.ProcessingException: com.adobe.ProcessingException: Problem accessing the data from Destination: dest:FP_ICF_DATA_X45//sap/bc/fp/form/layout/FP_FORM_SECURITY_TEST.XDP?fp-lang..
    IN Portal we are trying to execute any of the PDF rendering iView from ESS, we are getting the following error message.
    Error While Processing your Request :
    The call to URL has been terminated due to an error.
    http://<HostName>:<Port>/sap/bc/webdynpro/sap/asr_process_execuet/
    The Follwoing text was processed in System X45: WebDynpro Exception : ADS Call Failed ADS: com.adobe.ProcessingException: com.adobe.ProcessingException: Problem accessing the data from Destination: dest:FP_ICF_DATA_X45//sap/bc/fp/form/layout/FP_FORM_SECURITY_TEST.XDP?fp-lang..
    Could any one suggest something to work out on this issue.
    Thanks In Advance.
    Visweswar

    Hi Visveswara,
    I'm also getting the same kind of error on production system. The application is working fine in DEV & QAS.
    Pl share your inputs if you have any light on this.
    Regards,
    Indu.

  • Portugal Payment medium format - PS2 - configuration and custom program

    Hello,
    this is my first post here, so first of all "hi!" and second, sorry if this thread isn't in the right forum.
    I need to do a custom copy of the PS2 payment medium format, which is used in Portugal. It would be a short development, I just need that the line starting with ":08:" only appears when using a pre-defined payment method.
    I've seen that in the FBZP tcode, in the "Pmnt method in company code" customizing point, at the bottom there is this section, "Payment medium", where you can inform the Format (which it should be PS2) or the payment medium program (i think that for Portugal it's RFFOM100). You can only inform one option. Which one do you recommend? (I'm more used to work with purchase orders, so this are my first steps in the payment program)
    So my question is, in order to do this custom code, should it be a copy of the PS2 format (ZPS2?) or a copy of the RFFOM100 program? In any case, where can i look for the code section where to replace the standard SAP code for our custom program?
    Thank you very much!
    Warm regards,
    Gustavo

    Hi Gustavo,
    If you take a look in FBZP - Payment Method Country, you will see a "Payment Mathod" section. There you will have 2 payments programs type: Paymt Medium Workbench (PMW) and Classical.
    PS2 payment medium format is only used for PMW type and RFF* for Classical PM. These work to print and execute payments through F110.
    In my understading you should use PS2 because is the original need on your question.
    I hope I help you. Reply me if you have more questions.

  • Dev Workplace Installation failed in ADS configuration step

    Hi,
    I am installing Developer Workplace 7.01 in my system with MaxDB database. Its stopped at step 35/38 - Configure ADS with the following error:
    An error occurred while processing option SAP NetWeaver 7.01 Developer Workplace > Developer Workplace with MaxDB( Last error reported by the step :uncaught exception: nw.usageTypes.utlConnectionError: Execution of UTL tool 'C:\j2sdk1.4.2_19\bin\java.exe -classpath D:\usr\sap\UC2\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
    ORG081496/sapmnt/UC2/SYS/global/security/lib/tools/iaik_jce.jar;
    ORG081496/sapmnt/UC2/SYS/global/security/lib/tools/iaik_jsse.jar;
    ORG081496/sapmnt/UC2/SYS/global/security/lib/tools/iaik_smime.jar;
    ORG081496/sapmnt/UC2/SYS/global/security/lib/tools/iaik_ssl.jar;
    ORG081496/sapmnt/UC2/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/UC2/SYS/global/sltools/sharedlib/SLUtil.jar;D:\sapdb\programs\runtime\jar\sapdbc.jar -configured -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -log=UTL_configure_usages.log -action=true -sid=UC2 -dsn=jdbc/pool/UC2 -ssprops=D:/usr/sap/UC2/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/UC2/SYS/global/security/data/SecStore.key' aborts with return code 64 due to a database connection error. DIAGNOSIS: The connection parameters are wrong or the database server has been shut down. SOLUTION: Check 'UTL_configure_usages.log' and 'C:/Program Files/sapinst_instdir/NW701/SYSTEM/DEVWP/MAXDB/UTL.java.log' for more information. (in script unknown, line 0: ???)). You can now:
    Choose Retry to repeat the current step.
    Choose View Log to get more information about the error.
    Stop the option and continue with it later.
    Log files are written to C:\Program Files/sapinst_instdir/NW701/SYSTEM/DEVWP/MAXDB.
    I will attach further logs below:
    Thanks,
    Ajay

    UTL_configure_usages.log
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[UTL_configure_usages.log]/>
    <!PATTERN[UTL_configure_usages.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %7s: %m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Sep 6, 2010 10:52:06 AM  Info   : Successfully parsed!
    Sep 6, 2010 10:52:06 AM  Info   : Executing command Configure...
    Sep 6, 2010 10:52:06 AM  Info   : Establishing DB connection...
    Sep 6, 2010 10:52:07 AM  Path   : Exception : The DataBase is down or the connection parameters are wrong: -sid=UC2 -dsn=jdbc/pool/UC2 -ssprops=D:/usr/sap/UC2/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/UC2/SYS/global/security/data/SecStore.key -keyphrase=null
    java.lang.Exception
         at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1175)
         at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:423)
         at com.sap.exception.BaseException.<init>(BaseException.java:316)
         at com.sap.sl.ut.infoprovider.exceptions.UTInfoException.<init>(UTInfoException.java:99)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:361)
         at com.sap.sl.ut.manager.persistence.db.InfoManager.setConfigured(InfoManager.java:428)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.setConfigured(DataBaseInfoFactory.java:1376)
         at com.sap.sl.ut.manager.command.Configure.execute(Configure.java:30)
         at com.sap.sl.ut.manager.command.Command.exec(Command.java:90)
         at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:61)
         at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: Cannot connect to jdbc:sapdb://ORG081496/MXD [Task limit].
         at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:232)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
         at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)
         at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:359)
         at com.sap.sl.ut.manager.persistence.db.InfoManager.setConfigured(InfoManager.java:428)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.setConfigured(DataBaseInfoFactory.java:1376)
         at com.sap.sl.ut.manager.command.Configure.execute(Configure.java:30)
         at com.sap.sl.ut.manager.command.Command.exec(Command.java:90)
         at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:61)
         at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Sep 6, 2010 10:52:07 AM  Info   : Severe (database) error. Return code: 64
    Sep 6, 2010 10:52:47 AM  Info   : Successfully parsed!
    Sep 6, 2010 10:52:47 AM  Info   : Executing command Configure...
    Sep 6, 2010 10:52:47 AM  Info   : Establishing DB connection...
    Sep 6, 2010 10:52:47 AM  Path   : Exception : The DataBase is down or the connection parameters are wrong: -sid=UC2 -dsn=jdbc/pool/UC2 -ssprops=D:/usr/sap/UC2/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/UC2/SYS/global/security/data/SecStore.key -keyphrase=null
    java.lang.Exception
         at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1175)
         at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:423)
         at com.sap.exception.BaseException.<init>(BaseException.java:316)
         at com.sap.sl.ut.infoprovider.exceptions.UTInfoException.<init>(UTInfoException.java:99)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:361)
         at com.sap.sl.ut.manager.persistence.db.InfoManager.setConfigured(InfoManager.java:428)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.setConfigured(DataBaseInfoFactory.java:1376)
         at com.sap.sl.ut.manager.command.Configure.execute(Configure.java:30)
         at com.sap.sl.ut.manager.command.Command.exec(Command.java:90)
         at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:61)
         at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: Cannot connect to jdbc:sapdb://ORG081496/MXD [Task limit].
         at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:232)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
         at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)
         at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:359)
         at com.sap.sl.ut.manager.persistence.db.InfoManager.setConfigured(InfoManager.java:428)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.setConfigured(DataBaseInfoFactory.java:1376)
         at com.sap.sl.ut.manager.command.Configure.execute(Configure.java:30)
         at com.sap.sl.ut.manager.command.Command.exec(Command.java:90)
         at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:61)
         at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Sep 6, 2010 10:52:47 AM  Info   : Severe (database) error. Return code: 64
    Sep 6, 2010 10:54:18 AM  Info   : Successfully parsed!
    Sep 6, 2010 10:54:18 AM  Info   : Executing command Configure...
    Sep 6, 2010 10:54:18 AM  Info   : Establishing DB connection...
    Sep 6, 2010 10:54:19 AM  Path   : Exception : The DataBase is down or the connection parameters are wrong: -sid=UC2 -dsn=jdbc/pool/UC2 -ssprops=D:/usr/sap/UC2/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/UC2/SYS/global/security/data/SecStore.key -keyphrase=null
    java.lang.Exception
         at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1175)
         at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:423)
         at com.sap.exception.BaseException.<init>(BaseException.java:316)
         at com.sap.sl.ut.infoprovider.exceptions.UTInfoException.<init>(UTInfoException.java:99)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:361)
         at com.sap.sl.ut.manager.persistence.db.InfoManager.setConfigured(InfoManager.java:428)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.setConfigured(DataBaseInfoFactory.java:1376)
         at com.sap.sl.ut.manager.command.Configure.execute(Configure.java:30)
         at com.sap.sl.ut.manager.command.Command.exec(Command.java:90)
         at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:61)
         at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: Cannot connect to jdbc:sapdb://ORG081496/MXD [Task limit].
         at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:232)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
         at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)
         at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:359)
         at com.sap.sl.ut.manager.persistence.db.InfoManager.setConfigured(InfoManager.java:428)
         at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.setConfigured(DataBaseInfoFactory.java:1376)
         at com.sap.sl.ut.manager.command.Configure.execute(Configure.java:30)
         at com.sap.sl.ut.manager.command.Command.exec(Command.java:90)
         at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:61)
         at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Sep 6, 2010 10:54:19 AM  Info   : Severe (database) error. Return code: 64

  • ADS configuration in ABAP only system

    Dear Experts,
    We have SAP ERP EHP7 ABAP only server we want to configure ADS on this server
    1. can we configure ADS only ABAP system
    2. if yes then any additional license require and what is the configuration steps .
    Please guide me
    Regards

    Thanks you David for your reply
    Actually I don't have JAVA based system in my ERP DEV it is only abap based system it's version is sap ECC6 EHP7 .
    I have solution manager system it's version is 7.1 sr1 I want  to used it's java instance for ERP DEV ADS .
    I test program FP_TEST_00 from ERP DEV system it's working fine also
    FP_PDF_TEST_00                                      OK
    FP_CHECK_DESTINATION_SERVICE    OK
    FP_CHECK_HTTP_DATA_TRANSFER    ERROR
    FP_TEST_IA_01                                           ERROR
    Error is
    SYSTEM ERROR: ADS: com.adobe.ProcessingException: com.adobe.ProcessingException: Problem accessing data from Destination: dest:FP_ICF_DATA_DEV//sap/bc/fp/form/layout/FP_FORM_SECURITY_TEST.XDP?fp-language=DE(200,101)
    Regards

  • ADS configuration test fails

    Hi,
    I gone through the ADS configuration document for NW70 and all the settings are exactly same as described in the document but still I am getting the following errors during the check.
    1. When I execute test program "FP_TEST_00" I am getting below error,
    " ADS: com.adobe.ProcessingException: The rule specified,(200101) "
    2. When I execute destination service check using "FP_CHECK_DESTINATION_SERVICE" I am getting error as
    "SYSTEM Error: com.adobe.ProcessingException: The rule specified, requires Output PDF named: Nodes, does not exist."
    All other tests and configurations are working fine as mentioned in the configuration guide.
    Please help me on this issue.
    Regards,
    Nallasivam.D

    Hi
    I am also facing the same issue, can you let me know what was the problem ?
    Did you happen to resolve the issue ?
    Appreciate your inputs.
    Thanks
    Sri

  • Error getting when doing ADS configuration

    Hi ,
    We have in our project the portal is working as frontend & ECC is working as a backend.
    I have done with all the steps of ADS configuration ,when I checked the link
    http://host:port/webdynpro/dispatcher/local/TutWD_OnlineInteractiveForm/OnlineInteractiveFormApp
    but the error we are getting is "
    Details:   com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'local/TutWD_OnlineInteractiveForm' and application 'OnlineInteractiveFormApp' are not deployed on the server. Please check the used URL for typos."
    Can anyone please suggest for solution.
    Regards,
    Nilesh

    Hi,
         Check the following notes will help..
    0000717568
    0000724804
    0000736902
    0000867502
    0000894009
    0000910649
    0000944221
    0000967432
    0001004321
    It looks a lot.. but ti takes only few minutes to check each note.. it helped to configure my ADS.
    Cheers

  • ADS configuration problem

    Hi guys,
    I'm facing a problem with the configuration of the ADS.
    First I had only ABAP AS, my BASIS man installed for me a JAVA AS beside the ABAP.
    I didn't do any configuration for the ADS or any thing, I started with report FP_PDF_TEST_00 which gave me this error
    ADS:SOAP Runtime Exception: CSoapException Transport :(100101)
    Now I don't know really from where I should start my configuration, and bear in mind that I want to use only the Adobe Print Forms, I don't need interactive forms.
    Reagrds,
    Mahmoud

    Hello ,
       To start with ADS configuration , please check the
    ADS configuration guide provided by SAP -
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30a9630b-4f89-2a10-6fab-e311b3ffd9a6
    you can also take help from link
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/1094a46a-ce44-2a10-e7bf-b934ab505b0a [original link is broken]
    hope this helps.
    Thanks,
    Sahiba

  • MSS and ADS

    We are installing the MSS version of web dynpro.  We have a straightforward environment thus far with a portal server (J2EE WAS) and an R/3 server (ABAP WAS).   Accordingly we have installed the ESS and MSS java componenets on the portal server.  ESS installed and  working well with this arrangement.
    We are beginning install/config of MSS Adobe-based PCR's, and from what I can glean from documentation and experience, 2 things seem to be true:
    (1) the Adobe PCR forms themselves are resident within R/3 (probably included in a plugin), NOT in the java components (MSS or PCUI_GP) as one might expect
    (2) to render the forms, you must have Adobe Document Services (ADS) installed on the R/3 server--not just on another portal server.  ADS requires the J2EE add-in to the ABAP WAS.  Therefore, it seems that use of the new PCRs requires the J2EE WAS add-in. 
    For those of you who have implemented "new" MSS, am I correct in making the 2 statements above?

    Hello Dwight,
    let me try to at least answer parts of your question.
    - Yes, the ADS need to be deployed on a J2EE WAS to generate PDF based forms (e.g. PCRs) in MSS
    - You can deploy the ADS on any Web AS 6.40 J2EE engine. It does not need need to be installed on the R/3 server. Typically we install it on a separate machine. The ADS is called by MSS through Web Services. You just need to configure the Java and ABAP WAS according to the ADS configuration guide.
    - The MSS forms itself as well as the form integration framework (called ISR) is delivered as part of MSS
    Cheers,
    Matthias Zeller
    Sr. Product Manager
    Adobe Systems

  • Is my ADS configured ??

    I installed Developer Workplace and ADS has come along with it (atleast I think so). I went to
    http://localhost:50004/AdobeDocumentServices/Config and this is what is displayed. I know the format is all gone but bear with me please.
    AdobeDocumentServices
    Overview
    WSDL:
    http://localhost:50000/AdobeDocumentServices/Config?wsdl
    Description:
    Description not specified
    UDDI Publications:
    Service is not published
    Features:
    Design-time features for Port Type: AdobeDocumentServicesVi_Document
    Feature Property
    Name Value
    http://www.sap.com/webas/630/soap/features/transportguarantee Level No
    http://www.sap.com/webas/630/soap/features/authentication AuthenticationLevel None
    Deploy-time features for Binding: ConfigBinding
    Feature Property
    Name Value
    http://www.sap.com/webas/630/soap/features/transportguarantee Level No
    http://www.sap.com/webas/630/soap/features/authentication AuthenticationMechanism HTTP
    AuthenticationLevel None
    AuthenticationMethod BasicAuth
    SupportsSSO2Authentication false

    Hello,
    if you have NW04s the ADS is installed with the JAVA Stack in the standard.
    You have to manually configure this.
    Can you please check SAP note:
    #894009
    Here it is described where you can find the configuration guide.
    Best regards,
    Dezso

  • Trouble with ADS configuration: What is going wrong?

    Hi Experts,
    I need some help in configuring the ADS Call on Solution Manager 7.0 (First question: is ADS runable on Solution Manager - maybe that's the error...?). I only need printforms, no interactive forms.
    Java and Abap is running on one machine.
    This are the notes I've checked:
    944221
    894009
    1016404
    915399
    That's what I configured:
    1. There were no adsuser and ads_agent, so I created them, adsuser as system user, ads_agent as service user, both with the same pw. For ads_agent I assigned the roles SAP_BC_FP_ICF and SAP_BC_FPADS_ICF, for ads_agent the role ADSCALLERS. I had to create the role ADSCALLERS before.
    2. Assigning JAVA Security Roles: Visual Administrator - Cluster - Server - Services - Security Provider - User Management. There I have checked whether the user adsuser is assigned to the group ADSCALLERS and is unlocked. In Policy Configuration (still in Visual Admin) I checked component "com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar" and mapped user adsuser and ads_agent to the Security Role ADSCallers.
    3. RFC Connection: HTTP Connection to external Server (was available), Connection Type G, Target: our server, Servicenr 50400 (System Nr is 04), präfix is "/AdobeDocumentServices/Config?style=rpc", user is "ADSUSER", pw the same like in user master data.
    Testing the RFC Connection was successfull.
    4. Checking the services (SICF): fp and fpads are active.
    5. Visual Administrator: Creation of the connection from JAVA to ABAP: Visual Administrator - Cluster - Server - Destinations - HTTP. I created a new destination with name FP_ICF_DATA_/sap/bc/fp/form/layout/fp_test_00.xdp with username ADSUser and pw is working fine.
    I hope you guys can help. I'm working on this issue now for some days, without any improvement.
    What is going wrong and what did I forget to configure?
    Thanks in advance,
    Tan
    EDIT: In Visual Administrator the users ADSUSER, ADS_AGENT and SAP* are locked automatically after some time...
    Edited by: Tan Yildiz on May 10, 2011 10:51 AM

    Hi again,
    maybe you guys can help now.
    Point 6 is fixed partially:
    6. Execution of FP_TEST_00, FP_PDF_TEST_00, FP_CHECK_DESTINATION_SERVICE there comes a popup to enter the username and pw, without any ettect. After I entered the data 3 times the popup is closed and there comes the error
    After executing the reports the popup is not prompting any more. There comes the error immediately:
    ERROR CODE : 100.101
    ERROR MESSAGE : SOAP Runtime Exception: CSoapExceptionTransport : HTTP send returned with status code
    Fehler SOAP Framework: SOAP Runtime Exception: CSoapExceptionTransport : HTTP send returned with status code(100.101).
    I figured out the the error lies within the RFC Destination, but I have no idea where.....
    The target device is our server name (no http:...stuff, just the name "hanna") the service nr is 50400 (04 is the system nr) and path prefix is "/AdobeDocumentServices/Config?style=rpc"
    So long everythings seems to be ok for me.
    But by testing the destination there is nothing happening.....no reaction, no error, no warning, no success message.....other RFC connections are working.
    If I change the service nr to 50000 (there is another system where ads is working) the test result is a success message......
    Any idea whats going wrong? Thanks in advance

  • ADS Configuration Question

    Hello All,
    I am configuring the ADS in our ECC 6.0 system . I am facing two issues :
    Issue 1:
    I had completed all the steps for configuring ADS in the system. But when I run the Adobe form builder test from sfp transaction for the test form "FP_TEST_00" I am getting an error when executing the test function module for that test form saying :
    "Exception SYSTEM_ERROR
    Message ID: FPRUNX Message number:
    Message:
    ADS: com.adobe.ProcessingException: Problem accessing d(200101)
    What might be the issue???? We configured the Basic authentication and not SSL.
    Issue 2:
    Our J2EE is pointing to the client 001 and 800 is the ABAP development client .
    We had created a RFC destination by name "ADS" connection type "G" as part of the ADS configuration .
    IN SM59 when I do a test connection on both clients ADS Rfc destination is working only in client 001 (J2ee client) and not working in 800 client In client 800 it's telling the error " SR000 : ICM_HTTP_CONNECTION_FAILED".
    What might be the issue in 800 client?
    Thanks for your help in advance.
    Thanks,
    Greetson

    ISSUE 1:
    If not, then check this thread and run the tests mentioned in it at your end.
    Print Preview not working for Adobe forms
    ISSUE 2:
    Reason and Prerequisites
    You are using ICM Release 6.40 or higher for HTTP connections of the SAP Web AS. In other words, your kernel release is 6.40 or higher.
    Up to and including Release 7.00, ICM is only used in systems which also have an ABAP stack, and not in J2EE-only systems.
    You may also be using the SAP Web Dispatcher.
    Solution
    The note describes the following:
    Client and server roles of the ICM
    List of the various ICM timeout parameters
    Short description of the icm/conn_timeout parameter
    Description of "Processing timeout" and "Keepalive timeout"
    Configuration of the ICM parameters for the processing timeout and the keepalive timeout
    Timeout parameters in the SAP Web Dispatcher
    ICM kernel patches that affect timeouts
    There is detailed ICM documentation in the SAP Knowledge Warehouse.
    Client and server roles of the ICM
    The ICM can forward incoming HTTP connections for further processing to the SAP Web Application Server; the ICM then serves as the HTTP server. The ICM can also forward outgoing HTTP connections from the SAP Web Application Server to other HTTP servers; the ICM then serves as the HTTP client.
    Available parameters that control ICM timeouts
    icm/conn_timeout
    icm/keep_alive_timeout
    icm/server_port_< n >
    Parameter icm/conn_timeout
    icm/conn_timeout is used to set the timeout when setting up the connection. If the timeout is exceeded, an error page is generally displayed with the information "404 Resource not found" "Partner not reached".
    Therefore, exceeding the icm/conn_timeout does not lead to a "500 Connection timed out" error message.
    Processing timeout and keepalive timeout
    The icm/keep_alive_timeout and icm/server_port_< n > parameters define the keepalive timeout and the processing timeout.
    ICM distinguishes between these two types of timeout.
    The processing timeout is the timeout between the HTTP request being issued and the HTTP response being received.
    If the ICM is used as a server for the relevant HTTP request (in other words, when it forwards an incoming request to the SAP Web Application Server), the processing timeout is the time that the ICM will wait until a response is received from the SAP Web Application Server (ABAP or J2EE). This interval may be exceeded with long-running applications in ABAP or the J2EE engine.
    If the ICM serves as a client for the relevant HTTP request (that is, when it forwards outgoing requests from the SAP Web Application Server), the processing timeout is the time that the ICM waits until a response is received from the network. This interval may also be exceeded in the case of long-running applications in the network.
    The keepalive timeout specifies how long the network should remain open after a request has been processed successfully so that the TCP/IP connection does not have to be reestablished if additional requests are received.
    When you set the keepalive timeout, this does not normally lead to timeout errors. You should set the keepalive timeout high enough that the connection does not have to be reestablished for requests that are sent within a short time of each other, but low enough that the number of unused open TCP/IP connections is not unnecessarily high.
    Configuration of the ICM parameters for the processing timeout and the keepalive timeout
    For the ICM, the parameters mentioned here are in the instance profile.
    The processing timeout is set for individual services with the following parameter:
    icm/server_port_ < n > = ...,PROCTIMEOUT=< s >.
    The keepalive timeout can be set globally for all services of the ICM with the parameter icm/keepalive_timeout.
    You can also set it for individual services by using the following parameter:
    icm/server_port_ < n > = ...,TIMEOUT=< s >.
    If you set this parameter, it overwrites parameter icm/keepalive_timeout for the specified service.
    Even if the ICM serves as client for a request, the TIMEOUT and PROCTIMEOUT parameters of icm/server_port_ < n > control the timeouts for the relevant protocol, provided that you have set TIMEOUT or PROCTIMEOUT.
    If you have not set the PROCTIMEOUT parameter, TIMEOUT (or icm/keepalive_timeout) defines both the processing timeout and the keepalive timeout. Also, as of release 6.40, the keepalive timeout is limited to a maximum of 30 seconds.
    In a system where the default timeout settings of 30 seconds for the keepalive timeout and the processing timeout are not sufficient because of long-running applications, we recommend that you set the TIMEOUT and PROCTIMEOUT parameters for the relevant services so that you can configure them independently of each other. In addition, we recommend that you do not set the TIMEOUT value higher than necessary, for example, to the usual default value of 30 seconds.
    We recommend, for example, the following settings:
    icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600
    to allow a maximum processing time of 10 minutes.
    Timeout parameters in the SAP Web Dispatcher
    The same timeout parameters are available for the SAP Web Dispatcher as for the ICM. You can change the parameters of the SAP Web Dispatcher in the profile file of the SAP Web Dispatcher (for example, sapwebdisp.pfl). We recommend that you set the same parameters in the SAP Web Dispatcher and ICM.
    Known errors in ICM and Web Dispatcher timeout handling
    Since 6.40 patch level 64, there have not been any known errors in ICM and Web Dispatcher timeout handling.
    In Release 7.00, there are no known errors in ICM and Web Dispatcher Timeout Handling.
    Known Internet Explorer errors in the keepalive timeout handling
    Known errors in the keepalive handling from Internet Explorer are described in Note 900804. However, these errors are not usually displayed as timeout errors.
    KEVIN
    Edited by: Kevin Mike on Mar 14, 2008 11:44 AM

  • ADS configuration in iSeries

    Hello Exports,
      Greetings for the day,
    We are in the process of configuration of ADS in iSeries platform. Can you please guide us the configuration steps.
    We have downloaded the configuation guide and we have completed other platforms(like windows and solaris) ADS configurations without any issue.
    But the iSeries we don't have any help from documents. Please help on this.
    We have NW 7.0 EHP1 system with ABAP+JAVA in iSeries platform.
    please guide us..
    Thanks and Regards,
    Jibin.

    Hi Sai,
    Yes, I agree with your statement ADS always has configuration on ABAP and JAVA side nothing to do with the OS level.
    But in iSeries we require JAVA DI with other OS like windows or unix etc. JAVA engine in OS400 side ADS configuation will not work.
    We have configured one Windows Java dialog instance and now working fine. remains all the steps involved in ADS configuration is same.
    Please confirm if you are configured ADS in iSeries platform without any addtional DI in your organization/projects and please provide the configuration steps.
    Thanks for your reply.
    Thanks and Regards,
    Jibin.

  • ADS configuration Instance dialog iseries

    Hello I am confising about the configuration
    I have teh solman system  with  java + abap in  iseries  5v4 , I installed the  dialog instance java (Windows server Nº 10) Now I want to configurate the ADS in this system but i have  any questions:
    1.- in the guides are  steps about visual administrator  this  visual is the  solman system ??
    2.- Are the user ads_agent and ads_user  created in the 001 client?
    3.- this  test : http://:/AdobeDocumentServices/Config where is the name of the J2EE engine where the Adobe document services are installed, and is the port of the J2EE engine.
      Server and port  is the   dialog instance(Nº 10) or  solman system(nº 01)
    I have many problem with configuration or 
    How can I check  if  there are any problem  between  solman  system (abab + java) and  dialog instance (java)
    Thanks
    Danny

    Hello,
      Greetings for the day,
    We are in the process of configuration of ADS in iSeries platform. Can you please guide us the configuration steps.
    We have downloaded the configuation guide and we have completed other platforms ADS configurations without any issue.
    But the iSeries we don't have any help from documents. Please help on this.
    We have NW 7.0 EHP1 system with ABAP+JAVA in iSeries platform. please guide us..
    Thanks and Regards,
    Jibin.

  • ADS Configuration on ECC5

    Dears,.
    We have installed ECC5 on Windows 2003 with SQL server.After installation with sapinst I also installed ADS with credential file.
    Now when I am executing FP_TEST_00 to check ADS funtionality its not producing result so i am thinking that i have to do some post actions also after installing.
    Please suggest me what are the post actions i have to perform for it.
    Gyan

    Prakash,
    Check ADS configuration guide [here|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30a9630b-4f89-2a10-6fab-e311b3ffd9a6] and check if you have completed the same at your end.
    Chintan

Maybe you are looking for