SSO between EP and ECC-- JCo RFC Provider- Error-- JCO_ERROR_SERVER_STARTUP

Hello Everyone
I am setting Up SSO between my EP 7.0 and my ECC 6.0 system. During the phase JCO RFC PRovider i am giving the following values:
The following was done;
1. start Visual Administrator -> Service : Choose JCo RFC Provider
2. Created JCo RFC provider:
Program ID: SAPJ2EE_Port
Gateway host: EPDEV ( host of my EP System)
Gateway service: sapgw00
Server Count 5
Application Server Host: ERP6 ( Host of my ECC System)
System Number: 00
Client: 000
Language: EN
User: SAPJSF
Password: ..
When i click on SET i am getting the error " ERROR When ADDING TO BUNDLE" Check LOG FOR DETAILS".
I checked the DEFAULTTRACE.TRC and get the following MEssage :
Date , Time , Message , Severity , Category , Location , Application , User
03/01/2011 , 3:33:30:101 , Error changing bundle SAPJ2EE_PORT , Error , /System/Server , com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(BundleConfiguration conf) , , Administrator
03/01/2011 , 3:33:30:085 , com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Mar 01 03:33:30 PST 2011.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=SAPJ2EE_PORT GWHOST=EPDEV GWSERV=sapgw00
ERROR       partner 'EPDEV:sapgw00' not reached
TIME        Tue Mar 01 03:33:30 2011
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     1
I have configured my SLD as well. Any suggestions. Please Advise.

Hi Ahmed,
Please do check the validity of the certificate.
Please do cross check these steps again.
1.     Transaction u2013 STRUSTSSO2 (Trust Manager for Logon Ticket)
2.     Double Click Owner certificate. It gets reflected under the certificate tab.
3.                  Choose Format Binary
4.                  Choose File Path.
5.                  Enter the File Name
6.                 saved in local drive.
You can import into portal as x.509 certificate.
check this thread -
Certificate no longer has signature (use restriction)
Renew certificate via SAP MarketPlace, and install from tcode slicense. If you are working on a trial version, there is a SAP license request application form. Fill the form with the hardware key. you will get the new license via email. Install using slicense. Then try exporting the certificate.
Thanks,
Divya
Edited by: Divya V on Mar 10, 2011 11:25 AM

Similar Messages

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

JCO RFC provider and JCO connection

Hi all:
Please share your thoughts on the following doubts I have. Thanks.
1. To my understanding, we use JCO RFC provider(define in Java side) and RFC destination(in SM59) when we have request from ABAP to Java side. Then we use JCO destinations(define in Web Dynpro Content Admin) if we have request from Java to ABAP. Is this correct?
2. When creating the JCO RFC provider service, why we need to create those entries for repository for example, the server name, the user used to log into repository? What is the repository used for?
Thanks!

Hai,
your understanding of JCO RFC and RFC Destination is right.But JCO Destination gets the metadata and model data from ABAP,thats what we mention the Dictionany meta data and Application data while creating them.
Yes, we need to mention the application host,sys no,client and userdetails while creating the JCO RFC provider,then only it will fetch the data from that host and that particular client.
Thanks and Regards,

Problems with JCO RFC Provider in a cluster J2EE

Hello all,
We've defined a JCO RFC Provider because we need to call an EJB from a SAP R3 program. If I configure it in a J2EE with a unic server all works fine, but when I configure this scenario in a cluster J2EE (a central instance with two servers and a dialoge instance with three servers) it isn't working.
I've tried different configurations:
Configure the JCO RFC Provider in all the servers.
Configure the JCO RFC Provider only in one server, but this configuration is replied to the rest of the servers.
The previouse configuration, but stopping all the JCO RFC Provider services and starting it in a unic server.
Configure the JCO RFC Provider only in one server and checking "Local bundle" checkbox.
But it's not working... v_v
Has anyone configured a similar scenario? I don't know what is the correct way to configure it...
Thanks in advance...
jc!

Did you create the corresponding RFC connection in ECC transaction sm59 ?
with the same program ID.
both pointing on the same application host.
Regards,
Chris

SSO between Portal and Nakia.....problem with SSO... library not found..

Hi Sdn's and Nakisa tehnical experts,
We have a Portal environment 7.02 , a Nakisa environment 3.0 (CE) and and HR backend environment 701 (604).
We are busy setting up SSO between Portal and Nakisa via the, URL iview for the Org chart (http://<host>:<port>OrgChart/default.jsp).
We have done as indicated in wiki:
http://wiki.sdn.sap.com/wiki/display/ERPHCM/SAPSSOAuthenticationwithverify.pseusingSAPSSOEXT
We are however stil having issues with the SSO and in the cds.log the following is being displayed:
++01 Aug 2011 13:11:42 ERROR com.nakisa.Logger - com.mysap.sso.SSO2Ticket : Could not load library: sapsecu.dll - java.lang.Exception: MySapInitialize failed: rc= 14null++
++01 Aug 2011 13:11:42 ERROR com.nakisa.Logger - com.nakisa.framework.login.Credentials_SapSso : java.lang.Exception: MySapEvalLogonTicketEx failed: standard error= 9, ssf error= 0++
++01 Aug 2011 13:11:42 ERROR com.nakisa.Logger - com.nakisa.framework.login.Credentials_SapSso : Internal error (9) - No SSF error (0)++
Can someone indicate what I am doing wrong?
Regards Dries

Hi Luke,
thanks a lot for your help so far.
I have created a root/XML folder under the diretory, and the path is now as follows:
K:\usr\sap\NKP\J14\j2ee\cluster\apps\Nakisa\OrgChart\servlet_jsp\OrgChart\root\.system\Admin_Config\__000__Sasol_DEV_LIVE\.delta\root\XML
It seems like it finds the verify.pse, but not the library, sapsecu.dll.
My credentials.xml file is as follows:
<credentials>
<assembly name="SapSso"/>
<info>
    <item name="PseFilePath">XML\verify.pse</item>
    <item name="SsfLibFilePath">XML\sapsecu.dll</item>
    <item name="PsePassword"></item>
    <item name="WindowsPlatform">64</item>
    <item name="TicketFile"></item>
    <item name="Base64decode">true</item>
   </info>
</credentials>
I however stilll get the following in the cds.log
15 Aug 2011 13:59:53 INFO com.nakisa.Logger - Tenant ID: 000
15 Aug 2011 13:59:55 INFO com.nakisa.Logger - LoginSettingsObject Load: 1719
15 Aug 2011 13:59:55 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : Credential provider SapSso
15 Aug 2011 13:59:55 INFO com.nakisa.Logger - com.nakisa.framework.login.Credentials_SapSso : Using cert: K:\usr\sap\NKP\J14\j2ee\cluster\apps\Nakisa\OrgChart\servlet_jsp\OrgChart\root\XML\verify.pse
15 Aug 2011 13:59:55 INFO com.nakisa.Logger - com.nakisa.framework.login.Credentials_SapSso : Ticket is: AjExMDAgAA9wb3J0YWw6eXNzZWxhZ2OIABNiYXNpY2F1dGhlbnRpY2F0aW9uAQAIWVNTRUxBR0MCAAMwMDADAANEUDkEAAwyMDExMDgxNTExNDcFAAQAAAAICgAIWVNTRUxBR0P%2FAQQwggEABgkqhkiG9w0BBwKggfIwge8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGBzzCBzAIBATAiMB0xDDAKBgNVBAMTA0RQOTENMAsGA1UECxMESjJFRQIBADAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTEwODE1MTE0NzIwWjAjBgkqhkiG9w0BCQQxFgQUK13ubzFiQrY4H%2FLRk2ysyvPSvccwCQYHKoZIzjgEAwQuMCwCFF1W9d!tAjLvP8dnb1bs4XghaHSBAhQ9kd9N!bJubUWITtkzU!za96lxNg%3D%3D
15 Aug 2011 13:59:55 INFO com.nakisa.Logger - com.nakisa.framework.login.Credentials_SapSso : Version of SAPSSOEXT: SAPSSOEXT 4
15 Aug 2011 13:59:55 INFO com.nakisa.Logger - com.nakisa.framework.login.Credentials_SapSso : SCUE LIB base path is:
15 Aug 2011 13:59:55 ERROR com.nakisa.Logger - com.mysap.sso.SSO2Ticket : Could not load library: sapsecu.dll - java.lang.Exception: MySapInitialize failed: rc= 14null
15 Aug 2011 13:59:55 ERROR com.nakisa.Logger - com.nakisa.framework.login.Credentials_SapSso : java.lang.Exception: MySapEvalLogonTicketEx failed: standard error= 9, ssf error= 0
15 Aug 2011 13:59:55 ERROR com.nakisa.Logger - com.nakisa.framework.login.Credentials_SapSso : Internal error (9) - No SSF error (0)
15 Aug 2011 13:59:55 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : User to authenticate null
15 Aug 2011 13:59:55 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : Authentication provider SapSso
15 Aug 2011 14:00:00 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : User authenticated null
15 Aug 2011 14:00:00 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : Authentication row is {SapSsoTicket=AjExMDAgAA9wb3J0YWw6eXNzZWxhZ2OIABNiYXNpY2F1dGhlbnRpY2F0aW9uAQAIWVNTRUxBR0MCAAMwMDADAANEUDkEAAwyMDExMDgxNTExNDcFAAQAAAAICgAIWVNTRUxBR0P%2FAQQwggEABgkqhkiG9w0BBwKggfIwge8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGBzzCBzAIBATAiMB0xDDAKBgNVBAMTA0RQOTENMAsGA1UECxMESjJFRQIBADAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTEwODE1MTE0NzIwWjAjBgkqhkiG9w0BCQQxFgQUK13ubzFiQrY4H%2FLRk2ysyvPSvccwCQYHKoZIzjgEAwQuMCwCFF1W9d!tAjLvP8dnb1bs4XghaHSBAhQ9kd9N!bJubUWITtkzU!za96lxNg%3D%3D}
15 Aug 2011 14:00:00 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : User population provider is Database
15 Aug 2011 14:00:00 INFO com.nakisa.Logger - FunctionRunner : ensurePool : Current pool size:0
15 Aug 2011 14:00:00 INFO com.nakisa.Logger - FunctionRunner : ensurePool : Current pool size:0
15 Aug 2011 14:00:00 INFO com.nakisa.Logger - FunctionRunner.executeFunctionDirect: /NAKISA/RFC_REPORT took: 266ms
15 Aug 2011 14:00:00 INFO com.nakisa.Logger - BAPI_SAP_OTFProcessor_Report : WhereClause : ( (Userid is null) or (Userid='') ); Table : (SAP_UserPopulation); Dataelement : (UserPopulationInfo)
15 Aug 2011 14:00:00 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : User populated
15 Aug 2011 14:00:00 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : Role mapping provider is: SAP
15 Aug 2011 14:00:00 ERROR com.nakisa.Logger - SAPRoleMapping_SAP.MapRoles() : while trying to invoke the method java.lang.String.toUpperCase() of an object loaded from local variable 'value'
15 Aug 2011 14:00:00 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn : Login process finished with errors
Any ideas? Should I maybe hardcode the location in the credentials.xml?
Kind regards
Dries Yssel

SSO between Portal and Java WD application

Hi Experts,
I am using CE 7.2 on localhost and I am very new to SAP.
I need to know how can I get SSO between Portal and Java WD. I have a WD application that displays the logged in user using "IUser currentUser = WDClientUser.getCurrentUser().getSAPUser()", as well I can use "IUser user = UMFactory.getAuthenticator().getLoggedInUser()". Both work.
Q1. What is the difference in the 2 above?
Q2. My WD application is set to authenticate user. The WD application is in URL iView. I need SSO between Portal and WD application. Is there a way to get this SSO without SAP Backend (ECC), for now I just need SSO between Portal and Java WD appl.
Everything is in localhost.
Please advice. Thanks.

> need to know how can I get SSO between Portal and Java WD.
Then I suggest you ask your question in the Web Dynpro Java forum instead of the Web Dynpro ABAP one.

Error while loading service JCo RFC Provider

When I click on the "JCo RFC Provider" node under services in Visual administrator, I get an error:
"Error while loading service JCo RFC Provider"
Does anyone know what has gone wrong here, and how I go about fixing it?
Thanks in advance
Regards
Richard
PS. We're using EP6sp14

You have to use the correct Visual Admin version:
if your netweaver is 6.40 use VA 6.40 ... and for 7.00 the same, VA 7.00
(you get them from OS where netweaver is installed)
other possiblity: use Administrator login and check if it works, then correct your permissions (mostyl 'Administrators' group is missing)
Regards,
Chris

LCRSAPRFC is missing in Visual Admin (JCo RFC Provider)

H y,
I'm facing a problem while connecting our SolMan via RFC to SLD.
Found documents explainig how to set up connection to SLD.
SAPSLDAPI (was present in Abap and Java - wrong credentials - repaired)
LCRSAPRFC (only present as RFC CONN in ABAP, but missing in Java, Visual Administrator JCo RFC Provider
How can be the LCRSAPRFC added to JCo RFC Providers?
Do I have to create the RFC Conn LCRSAPRFC again in Abap/SM59 to get the LCRSAPRFC visible again in Visual Admin?
Thanks in advance
Tom

Hi,
Do I have to create the RFC Conn LCRSAPRFC again in Abap/SM59 to get the LCRSAPRFC visible again in Visual Admin?
Not Required.
LCRSAPRFC (only present as RFC CONN in ABAP, but missing in Java, Visual Administrator JCo RFC Provider
Usual Process
Maintaining the RFC Connections (Transaction SM59)
1. Log on to your SAP Exchange Infrastructure central instance host.
2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
RFC destination:LCRSAPRFC
Connection type: T
Description: <your description>
5. Choose ENTER
6. Choose the tab Technical settings and do the following:
a. Select Registered Server Program
b. In the Program ID field, enter: LCRSAPRFC_<SID>
where <SID> is the SAP system ID of your Integration Server host.
Use uppercase letters only.
c. Enter Gateway host and Gateway service of your Integration Server host.
To find out the required parameters:
a. On the Integration Server host, call transaction SMGW
b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and
gateway service)
7. Choose tab Special Options and select the flag Unicode in the box Character Width in
Target System.
8. Save your settings.
Java Stack
SAP J2EE Configuration for the Destinations (Visual Administrator)
1. On your SAP Exchange Infrastructure central instance host, start the SAP J2EE
Engine administration tool.
If you do not know how to start, see section How to start the SAP J2EE Administration Tool .
2. Choose Cluster u2192 Server u2192 Services u2192 JCo RFC Provider
3. In the section RFC destination, enter exactly the same program ID and gateway options for LCRSAPRFC that you used in the step Maintaining the RFC connection above.
Additionally, set the number of processes to 3.
4. In the section Repository, do the following:
a. Enter the parameter for the SAP XI host: Application Server, System Number, Client
and Language.
b. For User and Password maintain the login parameters for the user SAPJSF.
c. Select the flag Unicode.
6. Choose Set.
Testing
After you have maintained an RFC destination in both the ABAP and Java environment,
you can check it as follows:
1. Call transaction SM59 again.
2. Open your RFC destination.
3. Choose Test Connection.
No error should be displayed.
Regards,
Rao.Mallikarjuna
Edited by: Rao Mallikarjuna on May 31, 2008 11:40 AM

Question: Can Jco RFC Provider registers Program Id for BW7.3

Hello, Friends
I encounter the following issue and I wonder whether it is supported by Netweaver product. Please help answer.
My scenario is to create RFC (TCP/IP Connection) in ABAP server with program id registered by Jco RFC Provider (Visual Admin of NW7.02 Java)
If my ABAP BW NW server is 7.02 version, RFC can be tested successfully. However, for this time, I worked on another ABAP BW NW 7.3 Server and I create the RFC(TCP/IP Connection) with program id registered by Jco RFC Provider. As a
result, the RFC cannot find the program id registered by Jco NW 7.02 Java. Does Netweaver support ABAP 7.3 RFC with Program id registered by Nw 7.02 java Jco RFC provider?
Thanks a lot!
Welkin

Hi, Ejersbo
If you are using 7.3 portal, you can refer to the following on how to register Jco RFC provider on 7.3 Java:
(1) Open http://<server>:<port>/nwa
(2) Search for "Jco RFC destinations", open "Jco RFC destinations"
(3) Create a Jco RFC destination, with program id in the same name as the one which is used in your ABAP RFC in SM59
Welkin

JCO RFC Provider: "Bean not found" when calling EJB from ABAP via RFC

Hello,
I'm having trouble calling an EJB in a CE 7.1 system from ABAP via RFC. I'm trying to use the JCO RFC Provider service, which mean that I want to expose an EJB so that it can be called via Remote Function Call.
I have documented everything, including the code and the deployment descriptors I wrote, in this thread in the CE forum: Jco RFC Provider: Bean not found
If there's any chance you can help, please do me a favour and look into the problem.
Thanks a lot!
Thorsten

Hi Vladimir,
Thank you very much, your help was immensely valuable.
I just had to add the function declaration to the Home Component interface, everything else was correct, and now it works.
Cheers,
Thorsten

JCo RFC Provider Service

Hello
This topic may be not relevant to this forum but has anyone used JCo RFC Provider service for maintaining RFC Destinations?
What I am trying to do is to store the RFC Destinations over here and have a lookup on JCo RFC Provider service (or on its program id) from mapping tool.My code looks like
javax.naming.Context ctx = new InitialContext();
ctx.lookup("JCo RFC Service"); or
ctx.loopup("Program id name");
But while testing it gives Object Not Found exception.
I am expecting it to return JCO object which I can use to connect to SAP for executing RFCs.
Thanks in advance.
Regards
Rajeev

Hi rajeev,
Did u check if the Prog Id mentioned in JCo RFC provider is running (started in visual admin).
Did u perform ur lookup properly
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,"com.sap.engine.services.jndi.InitialContextFactoryImpl");
p.put(Context.PROVIDER_URL, "server:50004");
p.put(Context.SECURITY_PRINCIPAL, "Administrator");
p.put(Context.SECURITY_CREDENTIALS, "password");
javax.naming.Context ctx = new InitialContext();
ctx.lookup("JCo RFC Service");
Hope this helps you.
Cheers,
Siva Maranani.

JCO RFC provider: Server function not found, short dump

Hi all,
I'm trying to use the JCO RFC provider service of NW04s (SP15) together with an ABAP 4.6C system. I've followed all the documentation that I could find, but couldn't get it to work yet. This is what I've done so far:
Using SM59 I've had a destination APP_JK1 created for me on the R/3 system. AFAIK it's set up correctly and marked as a "registered server", connection tests were successful.
On the portal, I've created a RFC portal destination using my R/3 credentials and successfully tested it. Then I created an entry in the RFC provider service, using the correct values for system, id & gateway, and let it point to my RFC destination for the repository connection. The program ID is also APP_JK1.
Next, I created a stateless session bean which is part of an EAR, gave it a JNDI name of "RFCTEST" and added a method like this:
    * @ejb.interface-method view-type="both"
    * @param function called function
   public void processFunction(com.sap.mw.jco.JCO.Function function) {
      JCO.ParameterList input = function.getImportParameterList();
      String query = input.getString("I_STRING_SEARCH");
      JCO.ParameterList output = function.getExportParameterList();
      output.setValue(query, "ECHOTEXT");
(The project uses xdoclet for the creation of J2EE stuff)
In application-j2ee-engine.xml located in the META-INF directory of my EAR, I've added:
<reference reference-type="hard">
     <reference-target provider-name="sap.com" target-type="library">com.sap.mw.jco</reference-target>
</reference>
The application deploys without errors, and besides from my RFC connection works as expected. In the JNDI registry view of VisualAdmin I see the corresponding entry: "rfcaccessejb/RFCTEST" is a local reference to my stateless session bean.
On ABAP, I have a tiny little program that calls my function, mainly looking like this:
CALL FUNCTION 'RFCTEST' DESTINATION 'APP_JK1'
EXPORTING
    I_STRING_SEARCH = query
IMPORTING
    ECHOTEXT = t1.
Unfortunately, it short dumps immediately. The error message is:
JCO.Server could not find server function 'RFCTEST'
I'm lost. What could be wrong? Any help is greatly appreciated. Kind regards,
Christian Aust

Hello Perry song,
You got the short dump bcoz, there is no perform by the name you provided in the program,
for example. consider there are 2 programs.
Program 1 :
REPORT ZPGM1.
*Calling a perform SNAME1 , the code of perform is written in ZPGM2.
perform sname1 IN PROGRAM ZPGM2.
Program 2 :
REPORT ZPGM2.
perform sname1 .
Form SNAME1 .
write : 'Text in form SNAME1' .
endform.                    " SNAME1
(here SNAME1 is found and it works perfectly )
Change in Program 1 :
REPORT ZPGM1.
*Calling perform DELTA ,
perform DELTA IN PROGRAM ZPGM2 IF FOUND.
Now the perform statement will search for perform " DELTA " in ZPGM2 , but there is no perform by name DELTA , so here we need to mention the condition " IF FOUND " , so now by mentioning the condition " IF FOUND " in perform statement , if the perform DELTA is not found then it wont go to DUMP.
If condition " IF FOUND " is not mentioned in perform statement like
perform DELTA IN PROGRAM ZPGM2 . ( This gives DUMP )
just type " IF FOUND " when u r calling a perform from other program ( i guess this will solve the problem ).
Hope it might be helpfull,
Regards ,
Aby
Edited by: abhi on Nov 6, 2008 10:14 AM

Link between SRM and ECC invoice

Dear gurus,
I need to find the link between SRM and ECC invoice number, can you please provide me the related tables?
Thank you in advance for your collaboration.
Regards,
Fuffo

i don't have access to the system now but i guess will be table BBP_PDBEI.
or you can go tcode BBP_PD, check in item level.
cheers.

JCO RFC Provider problem

Hi!
We are having some problems in 2 PI 7.1 SP7 Development and Project
systems. Both have the same problem... We cannot see JCO RFC Provider
connections and we cannot create new JCO RFC connections.
Our Project system is copy of development and JCO connections are being
registered on Development causing some problems in proxy connections.
the problem is that we cannot change the JCO RFC connections on both
systems.
If I try to create a new JCO RFC Connection or even a dummy JCO connection it gives the error "The Program ID already exists. Type in an other name."
These systems are a SAP PI 7.1 upgrade from SAP XI 3.0. In version XI 3.0 the connections were OK.
In quality Assurance and Production we don't have this problem.
I've applied the latest AS Java patches but didn't changed the strange behaviour.
Have any one notice

In the default trace file we've found something like
"com.sap.engine.services.jmx.exception.JmxSecurityException: Caller <(>
<<)>some generated user id> not authorized, required permission missing"activate the UME super user, delete the deleted users, deactivate the UME super user and restart the system.
For further information you should see note 1261071

SSO between ITS and EP

We are implementing ESS MSS on 4.7 , ITS 4.7 with EP 6.0
Can some one point me as to how to configure the SSO between these various landscapes. I Think we would require SSO between EP and ITS for ESS in MSS services.
regards
Sam
Message was edited by:
sameer chilama

Hi Sameer,
All the information you are looking for is in the help.sap.com
http://help.sap.com/saphelp_nw04/helpdata/en/89/6eb8e1af2f11d5993700508b6b8b11/frameset.htm
This help guide is really very clear and thorough.
Regards
Daniel

SSO between EP and ECC-- JCo RFC Provider- Error-- JCO_ERROR_SERVER_STARTUP

Similar Messages

Maybe you are looking for