SSO for a Webdynpro App

Question

Hi Everyone hope you can help.
All i would like to know is:
If you have created a webdynpro and would like to bypass the default way of obtaining a JCO connection i.e)
Not using the GUI under the webdynpro admin console in the portal and defining the JCO (Meta and Model) there.
I have looked everywere and i can not find any documentation supporting "Writing your own JCO connection" inside the webdynpro app as a pooled connection.
I used to do it in EP5 like this:
public class Test {
private IPortalComponentRequest request;  //used for SSO
public void setRequest(IPortalComponentRequest value){
      request = value;
private void BuildConnection(){
      IJCOClientService clientService = (IJCOClientService) request.getService(IJCOClientService.KEY);
      poolEntry =
clientService.getJCOClientPoolEntry("PROD_SYSTEM", request);
      sapConnection = poolEntry.getJCOClient();*/ }
private void closeConnection(){
      poolEntry.release();
} //end Juan
The API that i used is not included in the webdynpro development lib.
Can anyone show me how to get the SSO cookie using the webdynpro API inside the webdynpro app. I need this cookie to include it into the required parameters during the JCO connection creation.
Thanks in advance!

Answer 1

Hi Diego
There is tons of information on this.
Check this post
Re: Problem accessing R/3 with SSO ticket from the EP6.0
and also links in this post.
For Web dynpro app to R/3 these simple points should help
-> Go to your Security provider service in VA , select the authentication template ticket and provide options for CreateTicketLoginModule with the one given in this document
http://help.sap.com/saphelp_nw04/helpdata/en/cb/ac3d41a5a9ef23e10000000a155106/content.htm
->Go to your key storage service in VA and export out the certificate and import this into R/3
->Go to your Content administration for Web Dynpro and switch the security settings in your JCO destinations to use 'useSSO' instead of userid and password , this applies only for the destination that fetches application data. The meta data destination can be configured to use userid and password.
Thats about it.
Regards
Pran
P.S is this '=(' the mexican hat