SAP - Web Logic Connectivity & Communication

I have been in SAP-ABAP for quite some time, all I know is ABAP & lil bit of Java
I have a requirement that needs immediate attention
In Layman terms can some one explain me
1. What is required inroder to set up connectivity between SAP ECC 6.0 to Web Logic 8.1 SP 4
2. What should I do to communicate with Weblogic to share data synchronously.
A brief description & detail info related links would be of great help.
Surely I'll leave feedback

Hello Vinod,
In order to set up connectivity between SAP ECC 6.0 to Web Logic 8.1 SP 4, you can use Iway 5.5 connector.
In Iway you can set up some communication channels. Each channel contains a Program ID (which refers to your RFC's ProgID) and the connection parameters to your SAP environment. By starting your channel in Iway, you check it in your SAP repository and the connection is established.
Let me know if you have other questions.
Micael.

Similar Messages

  • SAP Web AS connection Error

    Hello Guru's,
    we have a problem to connect our ERP (saperp) with EP (sapep).
    Following is show by the coneectiontest:
    SAP Web AS Connection
    Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the server to see if it is alive.
    7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    8. Checks HTTP/S connectivity to the defined back-end application
    Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (saperp.domain.com:8000)
    5. The host name saperp.domaint.com was resolved successfully.
    6. The server saperp.domain.com was pinged successfully.
    7. The Web AS ping service http://saperp.domain.com:8000/sap/bc/ping was pinged successfully.
    8. An HTTP/S connection to http://saperp.domain.com:8000sap/bc/bsp/sap was not obtained successfully; this might be due to a closed port on the Firewall.
    Test Connection with Connector works fine.
    Checks:
    -Connectiontest to saperp port 8000 with telnet works fine.
    -Service test of "http://saperp.domain.com:8000/sap/bc/ping" with browser works fine. ("Server reached successfully")
    -SSO works fine
    -All services for BSP are activated.
    -No Firewall are present between the Systems
    -ICMP are possible
    -Can't find some entry's in J2ee Log's
    -Sec. Audit prot. are no entry's
    i have no more ideas, can someone help?!
    regards
    Chris

    Hi,
    Don't worry : these test results are meaningless. You should test a real BSP application and see if it works.
    Regards,
    Pierre

  • System Configuration - SAP Web AS Connection - connection tests error

    hi
    I have a SAP ECC 6.04 and sap portal 7.01
    When I entered in option System Administration / System Configuration / System Landscape / Portal Content Tree / Systems / SAP_ECC (System created by me)
    I founded the following error (in  SAP Web AS Connection / Tests the connection to an SAP Web Application Server  )
    SAP Web AS Connection
      Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    7. Checks HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (htc-svr-erp.humantech.es:4200)
    5. The host name htc-svr-erp.humantech.es was resolved successfully.
    6. The Web AS ping service http://htc-svr-erp.humantech.es:4200/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.
    7. An HTTP/S connection to http://htc-svr-erp.humantech.es:4200 was not obtained successfully; this might be due to a closed port on the Firewall.
    ...also see a red "X" near a title SAP Web AS Connection
    I have other system (old system). It dont have the last error, I show the properties of  the "old system"(without error) and the "new system" (with error)  for your analisys
    In "old sap system",  stack java + abap
    http://img830.imageshack.us/img830/9755/oldsysstack.jpg
    In "new sap system", stack java separated abap
    http://img97.imageshack.us/img97/8627/newsysstack.png
    <u>In Portal</u>
    In "old system", I created "SAP_HCM" System
    In "new system", I created "SAP_ECC" System
    The "Connector" view  (<b><i>Object</i></b> Option)
    http://img706.imageshack.us/img706/3776/oldsysconnector.jpg (Old System)
    http://img269.imageshack.us/img269/914/newsysconnector.jpg (New System)
    *The "Internet Transaction Server (ITS)" view  (<b><i>Object</i></b> Option)
    http://img824.imageshack.us/img824/5043/oldsysits.jpg  (Old System)               
    http://img822.imageshack.us/img822/1314/newsysits.jpg (New System)
    The "User Management" View  (<b><i>Object</i></b> Option)
    http://img20.imageshack.us/img20/8646/oldsysuserman.jpg  (Old System)     
    http://img97.imageshack.us/img97/5339/newsysuserman.jpg  (New System)
    The "Web Application Server" View  (<b><i>Object</i></b> Option)
    http://img101.imageshack.us/img101/6155/oldsyswas.jpg (Old System)     
    http://img69.imageshack.us/img69/434/newsyswas.jpg (New System)
    My question of this view is: Is correct the Server port "4200" in New System? or Is correct the Server port "80+instance" in Old System?
    I run tcode RZ10 in backend after "Extended Maintenance"
    http://img15.imageshack.us/img15/8711/oldsysrz10.jpg (Old System)  (Here do not exist parameter icm/server_port_1 )
    http://img512.imageshack.us/img512/9268/newsysrz10.jpg (New System)  (Here do not exist parameter icm/HTTP/j2ee_0 ,  is it correct?)
    <i>Which of these two syntax is correct? 80 + instance or 4200 (any number of port)</i>
    also in SAP Systems, I run tcode SICF and enter in "Port Information"
    http://img265.imageshack.us/img265/5281/oldsysport.jpg  (Old System) (two ports)
    http://img441.imageshack.us/img441/7905/newsysport.jpg (New System) (three ports)
    The "Information" view (<b><i>Object</i></b> Option)
    http://img13.imageshack.us/img13/2012/oldsysinfo.jpg  (Old System)
    http://img714.imageshack.us/img714/6941/newsysinfo.jpg  (New System)
    My question is, Why in "Old System" the parameter "Created By" is "pcd_service"? is automatic?
    because the paremeter "Created by" is the user j2ee admin , I created the system manually or Should the user create pcd_service ?
    The "No Category" group  (<b><i>Object</i></b> Option)
    http://img827.imageshack.us/img827/8215/oldsysnoncat.jpg (Old System)
    http://img193.imageshack.us/img193/3800/newsysnoncat.jpg (New System) (in this System does not exist the parameter sysnr , is it correct?)
    The <i>"Permisions"</i> Option
    http://img825.imageshack.us/img825/886/oldsyspermin.jpg (Old System)
    http://img243.imageshack.us/img243/2057/newsyspermin.jpg (New System)     
    The <i>"Delta Link Tracer"</i> Option
    http://img716.imageshack.us/img716/798/oldsysdelta.jpg (Old System) (two levels)
    http://img828.imageshack.us/img828/8057/newsysdelta.jpg  (New System) (three levels, is it correct?)
    the other view the same (Old Sytem and New System)
    The <i>"Connection Test"</i> Option
    http://img412.imageshack.us/img412/5789/oldsystest.jpg
    http://img243.imageshack.us/img243/5237/newsystest.jpg
    Edited by: Ivan Quiroz on Sep 21, 2010 12:42 PM

    <br> <b><font color=blue> Excuse me, because the message Editor has problems, I edited with html tags for best view </font></b>
    <br>
    <br>hi
    <br>
    <br>I have a SAP ECC 6.04 and sap portal 7.01
    <br>
    <br>When I entered in option <b>System Administration /System Configuration /System Landscape / Portal Content Tree / Systems /SAP_ECC</b> (System created by me)
    <br>
    <br>I founded the following error (in  SAP Web AS Connection / Tests the connection to an SAP Web Application Server  )
    <br>
    <br> <b>SAP Web AS Connection</b>
    <br>  <b>Test Details:
    <br>The test consists of the following steps:
    <br>1. Checks the validity of system ID in the system object.
    <br>2. Checks if the system can be retrieved from the PCD.
    <br>3. Check whether a SAP system is defined in the system object
    <br>4. Validate the following parameters: WAS protocol; WAS host name
    <br>5. Checks if the host name of the server can be resolved.
    <br>6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    <br>7. Checks HTTP/S connectivity to the defined back-end application
    <br>
    <br>Results
    <br>1. The system ID is valid
    <br>2. The system was retrieved.
    <br>3. The system object represents an SAP system
    <br>4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (htc-svr-erp.humantech.es:4200)
    <br>5. The host name htc-svr-erp.humantech.es was resolved successfully.
    <br>6. The Web AS ping service http://htc-svr-erp.humantech.es:4200/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.*
    <br>7. An HTTP/S connection to http://htc-svr-erp.humantech.es:4200 was not obtained successfully; this might be due to a closed port on the Firewall.
    </b>
    <br>
    <br>...also see a red "X" near a title SAP Web AS Connection
    <br>
    <br>I have other system (old system). It dont have the last error, I show the properties of  the "old system"(without error) and the "new system" (with error)  for your analisys
    <br>
    <br>In "old sap system",  stack java + abap
    <br>
    <br><a href=http://img830.imageshack.us/img830/9755/oldsysstack.jpg>Stack Java + Abap<a>
    <br>
    <br>In "new sap system", stack java separated abap
    <br>
    <br><a href=http://img97.imageshack.us/img97/8627/newsysstack.png>Stack Java and Stack Abap</a>
    <br>
    <br><u><b>In Portal</b></u>
    <br>
    <br>In "old system", I created "SAP_HCM" System
    <br>In "new system", I created "SAP_ECC" System
    <br>
    <br>The <b>"Connector"</b> view  (<b><i>Object</i></b> Option)
    <br>
    <br><a href=http://img706.imageshack.us/img706/3776/oldsysconnector.jpg> (Old System)</a>
    <br><a href=http://img269.imageshack.us/img269/914/newsysconnector.jpg> (New System)</a>
    <br>
    <br>The <b>"Internet Transaction Server (ITS)"</b> view  (<b><i>Object</i></b> Option)
    <br>
    <br><a href=http://img824.imageshack.us/img824/5043/oldsysits.jpg>  (Old System) </a>               
    <br><a href=http://img822.imageshack.us/img822/1314/newsysits.jpg> (New System) </a>
    <br>
    <br>The <b>"User Management"</b> View  (<b><i>Object</i></b> Option)
    <br>
    <br><a href=http://img20.imageshack.us/img20/8646/oldsysuserman.jpg>  (Old System)     </a>
    <br><a href=http://img97.imageshack.us/img97/5339/newsysuserman.jpg>  (New System) </a>
    <br>
    <br>The <b>"Web Application Server"</b> View  (<b><i>Object</i></b> Option)
    <br>
    <br><a href=http://img101.imageshack.us/img101/6155/oldsyswas.jpg> (Old System) </a>     
    <br><a href=http://img69.imageshack.us/img69/434/newsyswas.jpg> (New System) </a>
    <br>
    <br>My question of this view is: Is correct the Server port "4200" in New System? or Is correct the Server port "80+instance" in Old System?
    <br>
    <br>I run tcode RZ10 in backend after "Extended Maintenance"
    <br>
    <br><a href=http://img15.imageshack.us/img15/8711/oldsysrz10.jpg> (Old System)  (Here do not exist parameter <i>icm/server_port_1</i> )</a>
    <br><a href=http://img512.imageshack.us/img512/9268/newsysrz10.jpg> (New System)  (Here do not exist parameter <i>icm/HTTP/j2ee_0</i> ,  is it correct?)</a>
    <br>
    <br><i>Which of these two syntax is correct? 80 + instance or 4200 (any number of port)</i>
    <br>
    <br>also in SAP Systems, I run tcode SICF and enter in "Port Information"
    <br>
    <br><a href=http://img265.imageshack.us/img265/5281/oldsysport.jpg>  (Old System) (two ports) </a>
    <br><a href=http://img441.imageshack.us/img441/7905/newsysport.jpg> (New System) (three ports) </a>
    <br>
    <br>The <b>"Information"</b> view (<b><i>Object</i></b> Option)
    <br>
    <br><a href=http://img13.imageshack.us/img13/2012/oldsysinfo.jpg>  (Old System) </a>
    <br><a href=http://img714.imageshack.us/img714/6941/newsysinfo.jpg>  (New System) </a>
    <br>
    <br>My question is, Why in "Old System" the parameter "Created By" is "pcd_service"? is automatic?
    because the paremeter "Created by" is the user <i>j2ee admin</i> , I created the system manually or Should the user create <i>pcd_service</i>?
    <br>
    <br>The <b>"No Category"</b> group  (<b><i>Object</i></b> Option)
    <br>
    <br><a href=http://img827.imageshack.us/img827/8215/oldsysnoncat.jpg> (Old System)</a>
    <br><a href=http://img193.imageshack.us/img193/3800/newsysnoncat.jpg> (New System) (in this System does not exist the parameter <i>sysnr</i> , is it correct?) </a>
    <br>
    <br>The <i><b>"Permisions"</b></i> Option
    <br>
    <br><a href=http://img825.imageshack.us/img825/886/oldsyspermin.jpg> (Old System) </a>
    <br><a href=http://img243.imageshack.us/img243/2057/newsyspermin.jpg> (New System) </a>
    <br>          
    <br>The <i><b>"Delta Link Tracer"</b></i> Option
    <br>
    <br> <a href=http://img716.imageshack.us/img716/798/oldsysdelta.jpg>(Old System) (two levels) </a>
    <br> <a href=http://img828.imageshack.us/img828/8057/newsysdelta.jpg>  (New System) (three levels, is it correct?) </a>
    <br>
    <br>the <i><b>"System Aliases"</b></i> Option
    <br>
    <br> <a href=http://img265.imageshack.us/img265/7574/oldsysalias.jpg> (Old System) </a>               
    <br> <a href=http://img256.imageshack.us/img256/9817/newsysalias.jpg>  (New System)  </a>          
    <br>
    <br>The <i><b>"Connection Test"</b></i> Option
    <br>
    <br>I based in  <a href= http://img64.imageshack.us/img64/6638/essalias.jpg> ESS SAP Documentation </a>
    <br>
    <br> In the seven point is diference (blue box) in the <a href=http://img412.imageshack.us/img412/5789/oldsystest.jpg> (Old System) (SAP_HCM System) (An HTTP/S connection to http://htc-svr-sap.humantech.es:8004 was obtained successfully.) </a> and <a href=http://img243.imageshack.us/img243/5237/newsystest.jpg> (New System) (SAP_ECC System) (An HTTP/S connection to http://htc-svr-sap.humantech.es:8004 was obtained successfully.)</a>
    <br>
    <br> I desactivated Firewall in my SAP Server and reviewed in <a href=https://forums.sdn.sap.com/thread.jspa?threadID=946905>SAP Forums </a> my problem but nothing
    <br>
    <br><b>Could This error also could be the problem that I get an error in the JCO Destination?</b>
    <br>
    <br> <a href=http://img819.imageshack.us/img819/826/oldsysjcosso.jpg>(Old System) (Succesfully)</a>                
    <br> <a href= http://img822.imageshack.us/img822/4226/newsysjcosso.jpg>(New System) (com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Issuer of SSO ticket is not authorized)</a>
    <br>
    <br> because I configure SSO correctly (I configured last year SSO in "Old System"),I run tcode SSO2
    <br>
    <br> <a href=http://img709.imageshack.us/img709/7194/oldsyssso2.jpg>(Old System)SSO2 Tcode</a>                
    <br> <a href=http://img830.imageshack.us/img830/9704/newsyssso2.jpg>(New System)SSO Tcode</a>                
    <br>
    <br> <a href=http://img185.imageshack.us/img185/9279/newsyssso22.jpg>(Old System) SSO2 Tcode Details</a>
    <br> <a href=http://img227.imageshack.us/img227/416/oldsyssso22.jpg>(New System) SSO2 Tcode Details</a>                
    <br>
    <br> <a href=http://img530.imageshack.us/img530/8710/newsyslog.jpg>(New System) In the SAP Logs: *** J2EE_ADM_DA1 | USERMAPPING.USE | USER.R3_DATASOURCE.J2EE_ADM_DA1 | | systemtype=[(none)], system=["UMESystemLandscapeDummy"], uses strong encryption=[false], remote user ID=[(none)] ***
    </a>

  • Error in SAP Web AS Connection Test

    Connection Test for Connectors is successful
    But
    SAP Web AS Connection
      Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the server to see if it is alive.
    7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    8. Checks HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (semdev.suzlon.com:8000)
    5. The host name semdev.suzlon.com was resolved successfully.
    6. <b>The server semdev.suzlon.com could not be pinged successfully.</b>
    What culd be the pblm ?

    Hi PK,
    in R/3 go to SE37 and check the FM RSBB_URL_PREFIX_GET it will show the details for WAS, I believe the details you gave for WAS are fine.
    Now for the issue go to T.Code SICF navigate to the webas path and activate the ping service. This will resolve the issue.
    Hope This helps.
    Cheers-
    Pramod
    Reward points if Helpful.

  • SAP Web AS Connection Problem

    Hi Gurus,
    I am now facing one problem about creating a system in EP.
    My system is Netweaver 04s with AS,EP and BI with SP13. All run in one single server.
    I maintained the SAP Web AS, and tested the connection, got the following message:
    Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the server to see if it is alive.
    7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    8. Checks HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (192.168.2.62:50000)
    5. The host name 192.168.2.62 was resolved successfully.
    6. The server 192.168.2.62 could not be pinged successfully.
    Strange that the ping fails, cause all the instances are running in the same server.
    "Connection Test for Connectors" works fine for me by using SSO from portal to abap.
    Please give the solution.
    Thanks & Regards

    Hi,
      You mean to say you are using IP address to login to portal. Using IP address has caused many problems. I am not sure if this would solve your issue but it is always recommended to use fully qualified domain name as host while accesssing portal. You can check using that too.
    Regards,
    Harini S

  • HA FAILOVER of web logic connection with SQL server

    Does Web-Logic support the HA Failover feature of the Microsoft SQL Server?
    In other words ,
    In case of a failover of the Microsoft SQL server's Primary node to the
    secondary,
    will the weblogic connection failover without having to re-connect again?
    Will the clients logging in or the clients already logged in will have to
    re-establish their connections?
    In an ideal scenario, SQL server failover from primary to secondary will not
    be effecting the client connections .

    Goutham Mallela wrote:
    The failover only kills the one DBMS instance while the secondary is still active
    ..all the client connections ideally should switch over..but iam not sure as
    said earlier if weblogic can do that as it uses JDBC to connect to the SQL server.Presumably the secondary is listening on a different port for connections, so a multipool
    would help you. One pool would be to the primary, and the other pool would be to
    the secondary. Every client request for a pool connection would go to the multipool.
    As long as the first DBMS is up (whenver it is up), connections will come from the
    first pool. Whenever the first pool cannot make a good connection, the multipool
    will return a connection from the second pool.
    Joe
    >
    >
    Joseph Weinstein <[email protected]> wrote:
    Quantos Quattro wrote:
    Are the two databases effectively identical?
    If so, will multipools not help you? (In availability-mode in this
    instance)if the one failure kills both dbms instances, then yes. If the failure
    kills connectivity to one dbms and not the other, then a multipool
    can help.
    Regards,
    Q
    "Goutham Mallela" <[email protected]> wrote in message
    news:[email protected]..
    Does Web-Logic support the HA Failover feature of the Microsoft SQLServer?
    In other words ,
    In case of a failover of the Microsoft SQL server's Primary node
    to the
    secondary,
    will the weblogic connection failover without having to re-connectagain?
    Will the clients logging in or the clients already logged in willhave to
    re-establish their connections?
    In an ideal scenario, SQL server failover from primary to secondarywill
    not
    be effecting the client connections .

  • WEB AS connection failed

    Hi,
    i have logon method in User management as SAPLOGON (since we have same userids in Portal as well as in BW systems) and issued the necessary parameters for WEB AS connection as :
    WAS Description BW Development
    WAS Host Name IP address:8000
    WAS Path /sap/bw/bex
    WAS Protocol http
    Also gave the all necessary values in connector property.
    Now if i go to Display - > Connection Test and select the following :
    SAP Web AS Connection
    Connection Test for Connectors
    it is giving the following result:
    Results
    SAP Web AS Connection - Jan 1, 1970 7:27:40 PM
    Test Details:
    The test consists of the following steps:
    1. Check that the system object defines an SAP system
    2. Validate the following parameters: wap.WAS.protocol; wap.WAS.hostname
    3. Check the HTTP/S connection to the defined backend application
    Results
    1. The system object represents an SAP system.
    2. The following parameters are valid: wap.WAS.protocol (http) ; wap.WAS.hostname (ip address:8000)
    3. HTTP/S connection failed. Make sure the protocol, host name, and user mapping are correctly defined.
    Test Connection with Connector - Jan 1, 1970 7:27:40 PM
    Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
    Results
    Retrieval of default alias successful
    Connection successful
    Even though we dont want to do user mapping (we have similar userids in both ends as mentioned early), i went ahead and did that also, but still WEB AS is failing with above mentioned error.
    Is there any specific patch level need to be there for BASIS or J2EE etc... we have BW 3.5(web as 640- ABAP System), EP 6.0 Patch 9.
    Thanks

    Hi ,
    I have had this problem before . Even though you still got a failure while the connection test , actually whrn you use the system object it works .Pls chaeck all the your parameter are right before you use this object .
    Thanks
    Aneez

  • Problem while creating SAP Web Dynpro iView

    Hi,
    I am creating SAP Web Dynpro iView from iView Template.
    The SAP Web Dynpro System Object is being created. The System Alias is also being created.
    The Test Connection is successful with Portal Server.
    Now, while creating SAP Web Dynpro iView from Template in Step 4:
    I am not getting my System while an old system which is being deleted is being displayed.
    Name of my System Object is: WD_System and System alias is: WD_Alias.
    The Step name is:
    Step 4:  Application Parameter
    Enter the paramater(s) of the application for which you want to create the iView 
    Regards
    Kaushik Banerjee

    Hi Bala,
    I am not getting the System Alias under:
    User Administration-> User Mapping-> Logon Data(Select a Principal) (System Alias).
    The System is successfully built under System Amininstration->System Configuration->System Landscape->Portal Content->kaushikb named WD_System and System Alias is named as: WebDynpro_alias.
    The Test Connection is successful.
    I am displaying the result below:
    SAP Web AS Connection
      Test Details:
    The test performs the following:
    1. Checks the validity of the system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Checks if a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the server to see if it is alive.
    7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    8. Checks HTTP/S connectivity to the defined back-end application
    Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (kolapon:50000)
    5. The host name kolapon was resolved successfully.
    6. The server kolapon was pinged successfully.
    7. The WAS ping service http://kolapon:50000/sap/bc/ping was not pinged successfully. If the ping service is not activated on the WAS, you can try to call the ping service manually.
    8. An HTTP/S connection to http://kolapon:50000 was obtained successfully.
    Regards
    Kaushik Banerjee

  • HTTPs connection from SAP WebAS

    Hello,
    I have to establish a connection from SAP WebAS to an iSaSiLk server via HTTPS.
    The iSaSiLk authentication is based on client certificates.
    I've created a SSL client PSE, generated the Certificate Request, imported the certificate response and the chain of certificates associated  with no errors. When testing the connection we're getting the following error message:
    SAP icm log:
    [Thr 1087400256] ->> SapSSLSessionInit(&sssl_hdl=0x2aaaba679980, role=1 (CLIENT), auth_type=3 (USE_CLIENT_CERT))
    [Thr 1087400256] <<- SapSSLSessionInit()==SAP_O_K
    [Thr 1087400256]      in: args = "role=1 (CLIENT), auth_type=3 (USE_CLIENT_CERT)"
    [Thr 1087400256]     out: sssl_hdl = 0x1a3310c0
    [Thr 1087400256] ->> SapSSLSetNiHdl(sssl_hdl=0x1a3310c0, ni_hdl=22)
    [Thr 1087400256] NiIBlockMode: set blockmode for hdl 22 TRUE
    [Thr 1087400256] <<- SapSSLSetNiHdl(sssl_hdl=0x1a3310c0, ni_hdl=22)==SAP_O_K
    [Thr 1087400256] ->> SapSSLSetSessionCredential(sssl_hdl=0x1a3310c0, &cred_name=0x1a49e4e0)
    [Thr 1087400256]   SapISSLComposeFilename(): Filename = "/usr/sap/XID/DVEBMGS00/sec/SAPSSLSPHTID.pse"
    [Thr 1087400256] <<- SapSSLSetSessionCredential(sssl_hdl=0x1a3310c0)==SAP_O_K
    [Thr 1087400256]      in: cred_name = "/usr/sap/XID/DVEBMGS00/sec/SAPSSLSPHTID.pse"
    [Thr 1087400256] ->> SapSSLSetTargetHostname(sssl_hdl=0x1a3310c0, &hostname=0x1a4a09e0)
    [Thr 1087400256] <<- SapSSLSetTargetHostname(sssl_hdl=0x1a3310c0)==SAP_O_K
    [Thr 1087400256]      in: hostname = "<remoteServer_to_be_accessed>"
    [Thr 1087400256] ->> SapSSLSessionStart(sssl_hdl=0x1a3310c0)
    [Thr 1087400256]   SapISSLUseSessionCache(): Creating NEW session (0 cached)
    [Thr 1087400256] Tue Jan 13 10:10:22 2009
    *[Thr 1087400256] *** ERROR during SecudeSSL_SessionStart() from SSL_connect()==SSL_ERROR_SSL*
    [Thr 1087400256]    session uses PSE file "/usr/sap/XID/DVEBMGS00/sec/SAPSSLSPHTID.pse"
    [Thr 1087400256] SecudeSSL_SessionStart: SSL_connect() failed
      secude_error 536871693 (0x2000030d) = "none of the PSEs registered with hSsl can suffice the negotiated SSL cipher suite"
    [Thr 1087400256] >>            Begin of Secude-SSL Errorstack            >>
    [Thr 1087400256] ERROR in ssl3_get_certificate_request: (536871693/0x2000030d) none of the PSEs registered with hSsl can suffice
    [Thr 1087400256] <<            End of Secude-SSL Errorstack
    [Thr 1087400256]   SSL_get_state() returned 0x00002150 "SSLv3 read server certificate request A"
    [Thr 1087400256]   No certificate request received from Server
    [Thr 1087400256] <<- ERROR: SapSSLSessionStart(sssl_hdl=0x1a3310c0)==SSSLERR_SSL_CONNECT
    [Thr 1087400256] ->> SapSSLErrorName(rc=-57)
    [Thr 1087400256] <<- SapSSLErrorName()==SSSLERR_SSL_CONNECT
    [Thr 1087400256] *** ERROR => IcmConnInitClientSSL: SapSSLSessionStart failed (-57): SSSLERR_SSL_CONNECT [icxxconn_mt
    On the iSaSiLk server we're getting:
    ssl_debug(2): Starting handshake (iSaSiLk 3.06)...
    ssl_debug(2): Received v3 client_hello handshake message.
    ssl_debug(2): Client requested SSL version 3.0, selecting version 3.0.
    ssl_debug(2): Creating new session 11:5F:04:C9:0D:32:15:B9...
    ssl_debug(2): CipherSuites supported by the client:
    ssl_debug(2): SSL_RSA_WITH_RC4_128_SHA
    ssl_debug(2): SSL_RSA_WITH_RC4_128_MD5
    ssl_debug(2): SSL_RSA_WITH_3DES_EDE_CBC_SHA
    ssl_debug(2): SSL_RSA_WITH_DES_CBC_SHA
    ssl_debug(2): SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
    ssl_debug(2): SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5
    ssl_debug(2): SSL_RSA_EXPORT_WITH_RC4_40_MD5
    ssl_debug(2): CompressionMethods supported by the client:
    ssl_debug(2): NULL
    ssl_debug(2): Sending server_hello handshake message.
    ssl_debug(2): Selecting CipherSuite: SSL_RSA_WITH_RC4_128_SHA
    ssl_debug(2): Selecting CompressionMethod: NULL
    ssl_debug(2): Sending certificate handshake message with server certificate...
    ssl_debug(2): Sending certificate_request handshake message...
    ssl_debug(2): Sending server_hello_done handshake message...
    ssl_debug(2): IOException while handshaking: Connection closed by remote host.
    ssl_debug(2): Sending alert: Alert Fatal: handshake failure
    ssl_debug(2): Shutting down SSL layer...
    ssl_debug(2): Closing transport...
    From the iSaSiLk everything seems to be OK, but on the SAP WebAS the error "none of the PSEs registered with hSsl can suffice the negotiated SSL cipher suite" is really unclear, since the cipher chosen by the iSaSiLk is one of the ciphers sent by SAP WebAS...
    Can anyone give me any suggestion?

    Hello Olivier,
    Thanks for your answer.
    I've implemented note 800240 which facilitates the PSE analysis by implementing the report ZSSF_TEST_PSE. With this report I'm able to check all the PSE content, which are:
    Filename            SAPSSLSPHTID.pse
    PIN                 <no>
    Signature           X
    Encryption          X
    Profile Parameter
    DIR_INSTANCE                   /usr/sap/XID/DVEBMGS00                       /usr/sap/XID/D00
    sec/dsakeylengthdefault                                                     1024
    sec/libsapsecu                 /usr/sap/XID/SYS/exe/run/libsapcrypto.so
    sec/rsakeylengthdefault                                                     1024
    ssf/name                       SAPSECULIB
    ssf/ssf_md_alg                                                              SHA1
    ssf/ssf_symencr_alg                                                         DES-CBC
    ssf/ssfapi_lib                 /usr/sap/XID/SYS/exe/run/libsapcrypto.so
    ssf2/name
    ssf2/ssf_md_alg                                                             SHA1
    ssf2/ssf_symencr_alg                                                        DES-CBC
    ssf2/ssfapi_lib
    ssf3/name
    ssf3/ssf_md_alg                                                             SHA1
    ssf3/ssf_symencr_alg                                                        DES-CBC
    ssf3/ssfapi_lib
    Environment variables
    USER                xidadm
    SECUDIR             /usr/sap/XID/DVEBMGS00/sec
    PSE
    Validity            18.12.2008 19:47:04   18.12.2009 19:47:04
    Algorithm           RSA (OID 1.2.840.113549.1.1.1)
    Test signature
    Signature OK
    Verification OK
    Test encryption
    Encryption OK
    Decryption OK
    As you can see, the cipher algorithm used is RSA. Any suggestion... ?
    An iSaSiLk server "is a Java programming language implementation of the SSLv2 (client-side), SSLv3, TLS 1.0 and TLS 1.1 protocols. It supports all defined cipher suites (except for Fortezza), including all AES and PSK cipher suites. iSaSiLk implements all standard TLS extensions, comes with an easy to use API and operates on top of the IAIK-JCE Javau2122 Cryptography Extension. iSaSiLk is highly configurable and will work with any alternative JCE implementation supported by a proper provider for supplying the required cryptographic algorithms".
    Once again thanks for your answer.

  • Communication problem between external web server and SAP WebAS

    Hello Experts,
    We are having a serious problem over here where we had one external server is pushing XML string using a HTTP-POST request to our SAP WebAS server (a BSP application is handling this request). We are not able to see the request coming to SAP i.e. SAP-BSP is not receiving XML.
    Also we found that, if request is routed through another proxy server (apache tomcat server redireting the request) connected through VPN to our network, it works but if the the same server is inside our network it doesn't. Rather in that case it never hits the Apache-Tomcat server itself.
    We tried to identify the network issue but it seems it is not the network or any firewall issue. When we had a small Echo server (itu2019s a small Java server) running on our SAP machine, we could see the request coming in. So it is definitely reaching the SAP server but the SAP Web AS is not picking up. Rather what we found that if the URL is simple e.g. http://<hostname>:<port> it works but if the URL is complex like something generated by SAP incase of BSP application it doesn't.
    Any idea what is causing this issue?
    I tried to look at SMICM trace files but got nothing. Any idea where would find the trace of incoming HTTP requests to SAP WebAS?
    Thanks in advance.
    regards
    rajeev

    Hi Rajeev,
    Pelase find the below link. i am not sure this is the exactly one for you. But i hope it'll help you.
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417800)ID0350917650DB11174011760851503410End?blog=/pub/wlg/10285
    http://www.sap-img.com/basis/basis-faq.htm
    Regards,
    CSK.

  • How to build a WEBI query on a SAP NANA OLAP connection?

    hi fellows,
    we all know that a relational connection can be built to SAP HANA database, and we build data foundation, biz layer to publish it to the repository, so that we can create a WEBI report based on a query to visit the universe.
    However, does anybody know how to create a WEBI query on a SAP HANA OLAP connection?  Since we don't need to build any data foundation on it.
    I created a sap hana olap connection, but failed to find anywhere to publish it?  Can anybody help?
    thanks,
    Jennifer

    Hi Jennifer,
    Check SCN thread http://scn.sap.com/thread/3493857.
    Also check below for Creating a SAP Universe on HANA: Best Practics.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00922ede-de2f-2f10-c2aa-f9b0f6495d34?overridelayout=t…
    Regards,
    JC

  • SAP and TAS Connection through Web Services

    HI Experts,
    we are planning to Integrate SAp and another TAS system using web services (no XI/PI). Please tell me if this way is correct.
    XML format of iDoc will be the data format, web service technology will be used to exchange data between SAP and TAS.
    To Transfer data to TAS, the client application running on SAP server will try to connect to the web service running on TAS server. Once connection is established, idoc data will be sent to TAS, then the connection will be closed.
    To transfer data to SAP, the client application running on TAS server will try to make connection to the web service running on SAP server. Once connection is established, idoc data will be sent to SAP, then the connection will be closed.
    tnx and regards
    Edited by: Technical Group on Dec 6, 2011 4:18 AM

    Hello,
    What will be you Language used for Connection.
    One method i may suggest is use ABAP FTP.
    With this push the files to a file sever location and read it using webservice.
    like wise let webservice generate a file and place a file in location and let ABAP prog pick the file.
    this way you can maintain a status flag for the number of records, thus having a staging area.
    regards,
    Abhishek

  • Remote Connection to SAP with SAP Web Dispatcher

    Dear Experts,
    i have installed a SAP Router + SAP ECC 6.0 IDES + SAP Portal 7.0 + SAP Solution Manager 7.0. The remote connection works.
    SAP Router is in a DMZ
    SAP ECC 6.0 IDES + SAP Portal 7.0 + SAP Solution Manager 7.0 are in another network only for SAP Systems
    Fo security reason, i would like to install a SAP Webdispatcher with the SAP Router's Server.
    I already:
    have extracted the icmadmin.sar file
    have executed the sapwebdisp -bootstrap command
    have started the web dispatcher with sapwebdisp pf=sapwebdisp.pfl
    have activated /sap/public/icman and /sap/public/icf_info/* services inthe SAP Solution Manager
    As the saprouttab file for the saprouter, i would like to establish the connection to SAP withe the SAP WebDispatcher.
    My questions are:
    What are the parameters i have to put in the sapwebdisp.pfl file?
    Do i have to create the PERMFILE and the AUTHFILE?
    Any example of profil file? (another than the SAP Library example)
    Thank you very much for your help in advance.
    Best regards.
    Pascal Tran.
    PS: Here is the sapwebdisp.pfl file
    Profile generated by sapwebdisp bootstrap
    unique instance number
    SAPSYSTEM = 50
    add default directory settings
    DIR_EXECUTABLE = .
    DIR_INSTANCE = .
    Accessibility of Message Servers
    rdisp/mshost = <Solution_Manager_hostanme>
    rdisp/msserv = sapms<Solution_Manager_SID>
    ms/http_port = 81<Solution_Manager_Instance_Number>
    SAP Web Dispatcher Parameter
    wdisp/auto_refresh = 120
    wdisp/max_servers = 100
    wdisp/shm_attach_mode = 6
    configuration for default scenario (medium size)
    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
    #maximum number of concurrent connections to one server
    wdisp/HTTP/max_pooled_con = 500
    wdisp/HTTPS/max_pooled_con = 500
    SAP Web Dispatcher Ports
    icm/server_port_0 = PROT=HTTP,PORT=8050
    SAP Web Dispatcher Web Administration
    icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt
    Hostname per default
    icm/host_name_full = <SAP_Router_Hostname>

    Hello,
    The two important paramters are covered in your profile.
    Accessibility of Message Servers
    rdisp/mshost = <Solution_Manager_hostanme>
    rdisp/msserv = sapms<Solution_Manager_SID>
    ms/http_port = 81<Solution_Manager_Instance_Number>
    And the port on which your webdispatcher listens from outside world.
    icm/server_port_0 = PROT=HTTP,PORT=8050
    For additional security you can use the https port also.
    I dont think you need to maintain any other file manually.
    I had configured web dispatcher but for 640 stack. It should be more or less the same.
    An example file sapwebdisp.pfl
    Profile generated by sapwebdisp bootstrap
    unique instance number
    SAPSYSTEM = 1
    Accessibility of Message Servers
    rdisp/mshost = <hostname>
    ms/http_port = 8101
    ms/https_port = 8005
    SAP Web Dispatcher Parameter
    wdisp/auto_refresh = 120
    wdisp/max_servers = 100
    wdisp/shm_attach_mode = 6
    configuration for default scenario (medium size)
    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
    #maximum number of concurrent connections to one server
    wdisp/HTTP/max_pooled_con = 500
    wdisp/HTTPS/max_pooled_con = 500
    wdisp/shm_attach_mode = 6
    SAP Web Dispatcher Ports
    icm/server_port_0 = PROT=HTTPS,PORT=1443
    icm/server_port_1 = PROT=HTTP,PORT=1081
    icm/HTTPS/verify_client = 0
    SAP Web Dispatcher Web Administration
    icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin
    DIR_INSTANCE = C:\Secudir
    ssl/ssl_lib = C:\Secudir\sapcrypto.dll
    ssl/server_pse= C:\Secudir\SAPSSLS.pse
    wdisp/ssl_cred = SAPSSLS.pse

  • SAP R/3 Connection in WEB AS 6.40

    Hello,
    I am currently in the process of <i>migrating our enterprise application from Jboss to SAPWAS 6.40</i>. One of the tasks is to get the SAP R/3 connectivity happening in SAP WAS server. We connect to the SAP R/3 system from our java classes and realise we have to use JCO to do this.
    is there a set of steps outlined anywhere which might tell me what is required to achieve the above? As in how do i go about setting the Connector Factory, getting hold of the relevant jars and dlls (if rquired)
    Any help is much appreciated and <b>promise to reward the person with any useful information</b>.
    Thanks
    Dushy

    Hi Bhavik, Much appreciate your response. At this stage I am not too concerned about how to call the RFC from our Java classes as we already had that in Place in Jboss. I am more concerned about how to go about declaring the JCO adapter. Here is an example from a *-ds.xml file in Jboss that we used to basically deploy our adapter into Jboss. Do we need a similar thing in Netweaver??
    <?xml version="1.0" encoding="UTF-8"?>
      <!-- ==================================================================== -->
      <!-- New ConnectionManager setup for firebird dbs using jca-jdbc xa driver-->
      <!-- Build jmx-api (build/build.sh all) and view for config documentation -->
      <!-- ==================================================================== -->
    <service>
      <mbean code="org.jboss.resource.connectionmanager.XATxConnectionManager" name="jboss.jca:service=XaTxCM,name=SAPConnectorFactory">
        <!make the rar deploy - A BIG HACK till xslt based deployment is written>
        <depends>jboss.jca:service=RARDeployer</depends>
        <depends optional-attribute-name="ManagedConnectionFactoryName">
          <mbean code="org.jboss.resource.connectionmanager.RARDeployment" name="jboss.jca:service=XaTxDS,name=SAPConnectorFactory">
            <!more hack>
            <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=SAPConnectorFactory</depends>
            <attribute name="ManagedConnectionFactoryProperties">
              <properties>
                <config-property>
                  <description>The client-number of the R/3 system</description>
                  <config-property-name>ClientNumber</config-property-name>
                  <config-property-type>java.lang.String</config-property-type>
                  <config-property-value>100</config-property-value>
                </config-property>
                <config-property>
                  <description>The name of the user, with which to logon to the system</description>
                  <config-property-name>UserName</config-property-name>
                  <config-property-type>java.lang.String</config-property-type>
                  <config-property-value>MDROVER</config-property-value>
                </config-property>
                          </config-property>
                <config-property>
                  <description>The name of the message-server (hostname or ip-address) for the R/3 system</description>
                  <config-property-name>MessageServerName</config-property-name>
                  <config-property-type>java.lang.String</config-property-type>
                  <config-property-value></config-property-value>
                </config-property>
                <config-property>
                  <description>The system-name of the R/3 system</description>
                  <config-property-name>SystemName</config-property-name>
                  <config-property-type>java.lang.String</config-property-type>
                  <config-property-value></config-property-value>
                </config-property>
                <config-property>
                  <description>The name of the group of application servers</description>
                  <config-property-name>GroupName</config-property-name>
                  <config-property-type>java.lang.String</config-property-type>
                  <config-property-value></config-property-value>
                </config-property>
              </properties>
            </attribute>
            <attribute name="JndiName">R3ConnectionFactory</attribute>
          </mbean>
        </depends>
        <depends optional-attribute-name="ManagedConnectionPool">
          <mbean code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" name="jboss.jca:service=XaTxPool,name=SAPConnectorFactory">
            <attribute name="MinSize">0</attribute>
            <attribute name="MaxSize">50</attribute>
            <attribute name="BlockingTimeoutMillis">5000</attribute>
            <attribute name="IdleTimeoutMinutes">15</attribute>
            <!--criteria indicates if Subject (from security domain) or app supplied
                parameters (such as from getConnection(user, pw)) are used to distinguish
                connections in the pool. Choices are
                ByContainerAndApplication (use both),
                ByContainer (use Subject),
                ByApplication (use app supplied params only),
                ByNothing (all connections are equivalent, usually if adapter supports
                  reauthentication)-->
            <attribute name="Criteria">ByContainer</attribute>
          </mbean>
        </depends>
        <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
        <!-- Include a login module configuration named SAPR3Realm.
             Update your login-conf.xml, here is an example for a
             ConfiguredIdentityLoginModule:
        <application-policy name = "SAPR3Realm">
           <authentication>
              <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
                 <module-option name = "principal">MDROVER</module-option>
                 <module-option name = "userName">MDROVER</module-option>
                 <module-option name = "password">BAPIRFC1</module-option>
                 <module-option name = "managedConnectionFactoryName">jboss.jca:service=XaTxCM,name=SAPConnectorFactory</module-option>
              </login-module>
           </authentication>
        </application-policy>
        NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
          module-option name = "managedConnectionFactoryName"
        must match the object name of the ConnectionManager you are configuring here.
        -->
        <!--comment out this line if you want component managed security or want
            to use the default values in the ManagedConnectionFactoryProperties -->
        <attribute name="SecurityDomainJndiName">SAPR3Realm</attribute>
        <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager</depends>
        <attribute name="TransactionManager">java:/TransactionManager</attribute>
      </mbean>
    </service>

  • FTP Server in SAP Web Application Server

    Hi,
    Would like to know if SAP Web Application Server comes with built-in FTP Server.
    Thanks

    Hi,
    FTP Server is not built in WAS. Integrate third-party products, tools, and applications, SAP Web Application Server supports several open connectivity standards, including the J2EE Connector Architecture and Microsoft .NET connectivity.
    A wide range of protocols and formats is supported for communication with SAP, non-SAP, and third-party components. SAP Web Application Server is open to the Common Object Request Broker Architecture (CORBA), Component Object Model+ (COM+), File Transfer Protocol (FTP), and SMTP to connect to non-SAP systems.
    IDoc and HTTP adapters sit on ABAP stack and the rest of the adapters(File, JDBC, SOAP etc) sit on JAVA stack.
    File Transfer Protocol (FTP) is an open protocol for exchanging files on a server.
    see this link:
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/43/0e16bfd7b021aee10000000a1553f6/frameset.htm">here</a> and
    <a href="http://help.sap.com/bp_bpmv130/Documentation/Planning/TechnicalInfrasture.pdf#search=%22SAP%20Web%20Application%20Server%20comes%20with%20built-in%20FTP%20Server%22">here</a>
    Regards, Suresh KB

Maybe you are looking for