Connecting to backend system with parameters

Hi,
i am able to get connected to bakend system with sytem number, portno, sid, host or ip... and can get transcation ivews with that...
ex: i am able to see perticular SAP R3 Transactional iview with these parameters
Then what is the purpose of  creating RFC destinations,  go.bat configuration, certificate creation and all those things.....
Thanks
Kumar.

Hi Kumar,
This things are needed when you want to access any service from R3 to Portal or vice versa. Like <b>Adobe Document Service (ADS)...</b>It should be installed in Portal server..and if you want to use ADS for displaying/printing R3 form in pdf format then you need to access ADS from Portal. For this type of case you need only the creation of RFC destination, go.bat configuration for HTTP destination, certificate..etc..
Thanks,
Sekhar

Similar Messages

  • User cannot connect to backend system with user J2EE_ADMIN.

    I am using Rapid Installer to initiate the second part of the installtion "ERP 6.0 EhP 3 – Self-Service Scenarios and Automatic Roles".  When I get to the J2EE User section to enter the parameters, the user is defaulted to "Administrator" and I enter my password.  I click next and get this message "User cannot connect to backend system with user J2EE_ADMIN."  Any ideas?

    If this is a double stack installation, you need to enter J2EE_ADMIN as user, NOT administrator.
    Markus

  • Connect to a backend system with the BI connector via Visual Composer

    Hi all,
    I set up a system landscape on my notebook with the NW2004s ABAP as NSP and with the NW2004s JAVA SP7 as J2E. Both systems are integrated in the SLD, this is set up. Furthermore I installed a BI system alias as NSP_XMLA in the portal with the URL for the backend system: http://localhost:8000/sap/bw/xml/soap/xmla.
    I have the same user on portal and backend system NSP. Both have admin previleges.
    When I try to logon to the backend system with this URL I get this error:
    "No switch to HTTPS occurred, so it is not secure to send a password"
    " Choose "Logon" to continue A dialog box appears in which you can enter your user and password"
    Then I can logon to the server and get a lot of XML.
    But I have to manually logon to the system.
    From the portal I cannot logon to the backend system with the test function. I get the error:
    Alias is found, but connection failed.
    I guess there must be an automatic logon preconfigured.
    How can I do this?
    Is SSO necessary?
    thanks for any help

    Hi Gregor,
    thanks for your answer, which was intersting but could not solve the problem. In the meantime I discoverd the reason for it.
    You have to insert the connection URL to the BW system at 2 points in the system.
    1. You have to configure the XMLA connector with the Visual Administrator.
    2. You must implement a system in the portal where you configure all necessary information, also the URL to the BW system.
    This seems somewhat strange to me because you will then not be able to connect with two or more BW systems to the portal and VC what is centainly necessary in a real world scenario. Anyway I can now see all Infoproviders of the BW system in the VC, and SSO isn't necessary because you configure the information to login to the BW system directly in the configuration of the XMLA connector in Visual Administrator.

  • BBPGETVD throwing an error -Backend system with release 701 are not support

    Experts,
    After changing the Backend connection from  R3 4.6c to ECC6 sysem in our BBPCRM4.0,
    the transaction "BBPGETVD" is not working, which is throwing an error as
    "Backend system with release 701 are not supported".
    Already we have applied some of the notes (822883 &862290)
    Thanks
    Ahamed

    Are you able to replicate other data like plants, product categories from the same backend system or are you facing the same error?
    Also please check the logical system and see if they are assigned to the client correctly. (in SPRO settings)
    Thanks,
    Prashanth

  • Failure to connect to backend system in Portal

    Hi Experts,
    I was hoping someone could help, quickly!!
    We are having an issue with transporting our VC model.  We are on VC 7.0 SP17
    I created a model in our development environment using a variable input form and adding the value help feature.  After we deploy in our dev environment the model looks perfect!!!
    We transported the VC model as an iview through the portal and we get a Failure to connect to back end system error.  We ruled out that it is not a transport problem using the portal.
    Can someone help!! 
    Thanks so much, Anna

    Hi Again,
    Thanks for both of your response, however, there is nothing in the log files andt we still have the Application error message, failure to connect to backend system.
    We were able to bypass the error and the model starts to "semi-function" - but we cannot access the characteristic through value help, we just get empty drop downs.   We all have the proper authorization in BI....
    Do you think there is a permission problem in the back end portal?
    Hopefully you can help.
    Thanks so much, Anna

  • Backend System with Release 701 are not supported

    SRM 5.0
    Extended Classic Scenario
    CCM 2.0
    When updating the vendors in SRM system using TC - BBPUPDVD getting the below error message :-
    Backend System with Release 701 are not supported
    Have checked in table - BBP_BACKEND_DEST, the backend entry is properly maintained.
    Can any one advice.
    Regards,
    Jayoti
    Edited by: SAP jayoti on Dec 7, 2010 1:11 PM

    The problem is resolved for vendor relication after applying the below notes 1313972 and 1372175.
    ECC sandbox seems to be in 701 release. When the backend system ECC is in release 701, vendor replication fails with the error message that 'Backend system release 701 not supported'. We need to apply notes 1313972 and 1372175 to fix this issue. I have applied them in Sandbox and the issue is resolved now.

  • Connect one Business system with two Integration Server

    Hello,
    Can we able to connect one Business System with two Integration Server?
    I have one Business system (ECC 6.0 with the client 900) and it is already connected with PI 7.0 system.Can I able to connect the same sytem (with same client) with PI7.1?
    I want to do the HTTP Connection for ABAP Proxy for this two XI system with one business Sytem ?
    Is this possible ?Is there any work around solution there?
    Thanks.

    Hello ,
    This document describes about connecting with Two PI7.1 system using Application Server 7.1 and Application Server 7.0 SP14  .
    I want to connect same ECC system via abap proxy with two different PI system .One is PI7.0 and another one is PI7.1 system.
    Is this possible if i use Application Server 7.1 or Application Server 7.0 SP14  ?
    Thanks.
    Lakshmi
    Edited by: Muthulakshmi Pandi on Apr 16, 2009 11:48 PM
    Edited by: Muthulakshmi Pandi on Apr 17, 2009 12:21 AM

  • Could not connect to backend system through portal via Web Dispatcher

    Web dispatcher redirecting problem
    Dear Experts,
    I have implemented a scenario which comprised of customizing that is developed in Portal EP7. What customizing does is getting report from backend system (ERP 6.0)
    According to the needs for reaching the portal from internet I configured the SAP Web Dispatcher in the environment as you may see its contents below.
    The problem is when I run the customizing in portal system then it requires connecting to backend system (ECC 6.0) to get the data (report). But from this point on web browser comes to a blank page, could not view the data that is from backend system via portal. Because in the time when it tries to retrieve data in backend system, on the left bottom of the explorer the indicator shows internet address that system uses connecting to the backend system as local network address of the backend system which is not known in internet therefore I get blank page.
    The question is how to configure the web dispatcher in a way that both portal and backend systems could be reachable from internet?
    Contents of profile file of Web Dispatcher as;
    SAPSYSTEMNAME = WDP
    SAPGLOBALHOST = portald
    SAPSYSTEM = 02
    INSTANCE_NAME = W02
    DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
    DIR_EXECUTABLE = $(DIR_CT_RUN)
    Accesssability of Message Server
    rdisp/mshost = portald
    ms/http_port = 8101
    Configuration for medium scenario
    icm/max_conn = 500
    icm/max_sockets = 1024
    icm/req_queue_len = 500
    icm/min_threads = 10
    icm/max_threads = 50
    mpi/total_size_MB = 80
    SAP Web Dispatcher Ports
    #icm/server_port_0 = PROT=HTTP,PORT=81$$
    SAP Web Dispatcher Ports
    icm/server_port_0 = PROT=HTTP,PORT=60000
    icm/HTTP/redirect_0 = PREFIX=/, TO=/irj/index.html
    icm/HTTP/redirect_0 = PORT=50000
    #maximum number of concurrent connections to one server
    wdisp/HTTP/max_pooled_con = 500
    wdisp/HTTPS/max_pooled_con = 500
    Configuration for medium scenario
    icm/max_conn = 500
    icm/max_sockets = 1024
    icm/req_queue_len = 500
    icm/min_threads = 10
    icm/max_threads = 50
    mpi/total_size_MB = 80
    Regards,
    Ali Taner

    Hi,
    To resovle this you must have registered FQDN for your backend system as well. When you call the report from Portal using internet it should call that FQDN of your backend system then DNS will resolve this & you will get the expected page. This way only you can resolve this issue.
    Thanks,
    Sachin Sable

  • BBPGETVD - error:backend systems with release 700 are not supported

    Hi,
    When I am trying to replicate vendor data from EEC to crm 4.0 via BBPGETVD.
    I get the error message"backend systems with release 700 are not supported"
    Is anyone have Idea what is wrong? and how can fix it?
    Thanks,
    Rachel

    Yossi,
    I believe that standard transaction does not work with ECC 6.0.  The standard response would be to upgrade your CRM system to 5.0 so that you can download vendors from ECC 6.0.
    Bascially the vendor replication programs in CRM below 5.0 aren't really that reliable for delta downloads(one error will cause an entire load to fail).  So you probably at best should copy the SAP standards to generate custom load programs as a starting point.
    It is not too difficult and overcomes some of the restrictions that SAP puts in place(i.e. you can only use one number range for vendors downloaded, etc.).  This is definitely one of the weak points of CRM 4.0 that was fixed in CRM 5.0.
    If you have more questions on this let me know.
    Take care,
    Stephen

  • 'Backend systems with Release 701 are not supported'

    while BBPGETVD transaction is run below error is seen,
    'Backend systems with Release 701 are not supported'
    Please help to resolve it.

    Hi
    What is your backend system ECC version?
    What is the configuaration in Define back end system?
    Note 1313972 - BBPGETVD: Backend system latest release not supported
    br
    muthu

  • "Backend systems with Release 701 are not supported " - ECC 6.0  to SRM 5.0

    Hi ,
    I have 2 doubts .
    1. We are getting Error "Backend systems with Release 701 are not supported "  while replicating vendors from ECC 6.0 backend system to  SRM 5.0 system.
    There are some notes on simillar topic but are not for SRM 5.0 ,suggested on SDN. an anyone please suggest what need to be done  for the same.
    2. Can we  replicate Vendor Master Data with Contact Person  from SRM to ECC system ? if yes, How ?
    Regards
    Narendra

    answer 1:-
    Note 1372175 - BBP_VENDOR_GET_DATA_JOB "Back-End Systems Not Supported"
    On recent upgrade of the ECC back-end system to release '701' the program BBP_VENDOR_GET_DATA_JOB is getting errored out. If you are using SRM 5.0 , SRM_SERVER 550 with ECC backend Release 701 you encounter the above reported problem
    Other terms
    Vendor Replication Job, Release 701, Backend not supported, BBP_VENDOR_GET_DATA_JOB
    Reason and Prerequisites
    The program does not consider the release 701
         remote_release EQ '700' OR remote_release EQ '701'.
    OR
    bbp_vendor_get_data - DEBUG what ois the remote_release 700 or 701?
    Muhtu

  • Webinar- Connect Third Party Systems with SAP B1 – DI API, DI Server, B1WS

    Webinar happened on 21st August.
    Get the Presentation, Video recording and answers of all the questions asked in the webinar through the below link.
    Webinar- Connect Third Party Systems with SAP B1 - DI API, DI Server, B1WS

    Hi Oleksiy,
    I don't see anything strange in your code. You should receive an error message but it shoudn't loop without end ;o(
    The only thing I can propose you is to create a message for support, they will have a deepest look into your problem.
    Regards
    Trinidad.

  • Creation of multiple connectors if we have backend systems with multiple

    Hi All,
    If I have 5 backend systems with 2 clients each.
    Do I need to create UWL connector for each client.
    Regards
    Suneel

    Hi,
    You have to create a connector for each system alias. So if you have a backend with 2 clients and you want to retrieve work items from both clients you will have to create 2 systems (and 2 aliases) and 2 UWL connectors.
    Regards,
    Pierre

  • Mac is not connecting to network systems with names it's only connecting with the IP address why?

    Mac is not connecting to network systems with names.
    It's only connecting with the IP address why?

    It sounds like a problem with the domain name server. Be sure you are using the correct DNS in System Preferences > Network, and if you are make sure it is functioning correctly.
    Best of luck.

  • Steps to connect a CRM system with MDM

    Hi everybody,
    I've got a problem here : I should build a connection between a CRM system and MDM (get the data in several tables in the CRM system, normalize them in MDM and then put them back in the CRM).
    What would the steps I've got to do to achieve that ? Do I need XI between the two systems ? Do I have to map the tables before sending them in MDM (and how could I do that ?)
    Thank you for all the help you can give me
    Seb

    Hi
    The Universal Worklist (UWL) iView is part of the KMC (Knowledge Management and Collaboration), capability of SAP NetWeaver. The integration of the SAP NetWeaver MDM workflow with UWL will be provided with SP04. This will provide the ability to expose SAP NetWeaver MDM workflow steps in the SAP Universal Work List (UWL). These jobs may run from the BPM process or can be launched inform within SAP NetWeaver MDM. UWL is defined as the main consolidated ”Inbox“ for SAP users, being the main location to monitor jobs directly activated in SAP NetWeaver MDM, or connected to a process that integrates with SAP NetWeaver MDM.
    Using the SAP NetWeaver Portal UI, show a summarized list of all workflow (WF) jobs/tasks from all systems of SAP NetWeaver MDM Landscape per user - one single UI for all my tasks. The UWL is already integrated with other major SAP products, like R/3, SAP CRM, mySAP ERP, etc.
    https://sapportal.wdf.sap.corp/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/infocenters/ws%20ptg/ptg/platform%20ecosystem/industry%20standards/projects%20and%20programs/business%20process%20management/index.html
    First of all, you must set a RFC connectivity between CRM and backend system:
    o     Create system users for remote connection (RFC_CONN). This user must have SAP_ALL authorization.
    o     Create RFC connections in CRM system.
    Go to transaction SM59 on CRM side and click on 'create' button. Set RFC destination name to the back-end system <sid>CLNT<client> (eg. R3DCLNT200), connection type to 3 (abap / R/3 connection) and fill the target host to your back-end system. On the Logon/Security tab, add the RFC_CONN user created in the previous step. Save your settings.
    o     Create RFC connections in the back-end system.
    Go to transaction SM59 on the back end and click on 'create' button. Set the RFC destination name to CRM system <sid>CLNT<client> (eg. CR1CLNT300), connection type to 3 (abap / R/3 connection) and fill in the target host to your back-end system. On the Logon/Security tab, add the RFC_CONN user created in the previous step. Save your settings.
    o     Create a logical system name in CRM.
    Go to transaction SPRO -> SAP Implementation Guide -> Customer Relationship Management -> CRMServer -> Technical Basic Settings -> ALE Settings -> Distribution -> Basic Settings -> Logical Systems -> Define Logical System Add a new value:
    Save your settngs.
    o     Create a logical system name in the back end.
    Go to transaction SPRO -> SAP Customizing Implementation Guide -> SAP Web Application Server -> Application Ling Enabling -> Sending and Receiving Systems -> Logical Systems -> Define Logical System Add a new value:
    Save your settngs.
    2.     
    3.     Middleware parameters setup Go to transaction SM30 on backend system and choose table CRMCONSUM. Add the following values:
    4.     Next, choose CRMSUBTAB for subscription table for the Up and Download Object and add the following values
    User     ObjectName     U/D     Obj. Class     Function     Obj. Type     Funct. Name
    CRM     empty     Download     Material     empty     empty     CRS_MATERIAL_EXTRACT
    CRM     empty     Download     Material     empty     empty     CRS_CUSTOMIZING_EXTRACT
    CRM     empty     Download     Material     empty     empty     CRS_SERVICE_EXTRACT
    Next, choose CRMRFCPAR for definitions of RFC Connections and add the following values
    User     ObjectName     Destination     Load Type     INFO     InQueue Flag     Send XML
    CRM     *     SR1CLNT300     Initial Download     SR1CLNT300     X     Send XML
    CRM     *     SR1CLNT300     Request     SR1CLNT300     X     Send XML
    CRM     MATERIAL     SR1CLNT300     Initial Download     SR1CLNT300     X     Send XML
    Leave all other field empty.
    Now, configure filtering for the material master:
    Choose the CRMPAROLTP table for CRM OLTP Parameters and add the following values:
    Parameter name     Param. Name 2     Param. Name 3     User     Param. Value     Param. Value 2
    CRM_FILTERING_ACTIVE     MATERIAL     empty     CRM     X     empty
    Now we must edit the table for the application indicator. Go to transaction SE16N on the back-end side and choose table TBE11. Search or add an application component BC-MID and edit activity settings (field AKTIV = X).
    Save your settings.
    8.     Enterprise buyer with/without CRM In this activity, you define whether you are running the Enterprise Buyer and CRM in the same system. This might accelerate the Master Data download performance. If you are using CRM in the client, then skip this activity.
    In the CRM system run transaction BBP_PRODUCT_SETTINGS, deselect 'Test mode' and choose the Execute button.
    The system generates a report containing all tables that have been deactivated.
    9.     Generate repository objects With this procedure, you generate the middleware function modules (BDoc Object Type) for the material master.
    Go to transaction SMOGGEN and choose object PRODUCT_MAT and PRODUCT_SRV. Generate services for all object categories.
    Please let me know your email id, i shall send you this document
    Regarsd
    Rehman
    Reward Points if Useful

Maybe you are looking for