RFC: INTEGRATION_DIRECTORY_HMI

Hi all,
We are facing a problem with opening IB main page.
We restarted J2EE server yesterday. after restart the "SXMB_IFR" is NOT working. the URL is
"http://icfxi1:50000/rep/start/index.jsp". we checked Telnet IP address with service 50000. message saying "TEST FAILED". Whereas in SICF port information for HTTP only 8000 port is available. this port is recognizing in Telnet.
at the same time, while testing
the RFC connection "INTEGRATION_DIRECTORY_HMI"with connection type "H"
status bar message saying "ICM_HTTP_CONNECTION_FAILED"
What could be the possible reason?
Thanks in adv.
Rajesh Y.

Hi Nagarjuna,
The data displayed in the link mentioned by you is as follows:
Application Server State
HTTP Application Server Handler
ABAP Server operational = TRUE
J2EE Server configured = FALSE
J2EE HTTP port =
J2EE HTTPS port =
J2EE Server operational = FALSE
Default root access handler = ABAP
URL Prefix Table loaded = TRUE
It says that J2EE server is not configured and the values for J2EE HTTP port is blank.
What does this data indicate?
Regards
Rajesh Y

Similar Messages

Forbidden error on Testing HTP RFC : INTEGRATION_DIRECTORY_HMI

Hi All,
While testing the HTTP RFC (INTEGRATION_DIRECTORY_HMI) its throwing 403 Forbidden error.
I recheked all the entries in it and every thing looks fine.
Because of this error i guess i am not able to login to IR & ID using XISUPER (which is having all the roles ) even.
the same error follows Not Authorised.
Please help me resolve this.
Regards,
Mahesh.

Hi Uma,
-->Check the path prefix whether you had maintained or not and also maintain the proper host name and service number.
-->below is the path prefix
/dir/hmi_cache_refresh_service/ext and service number 5 + instance number + 00.
-->recheck by maintaining the above settings.
Thanks

Problem with RFC INTEGRATION_DIRECTORY_HMI

Hello !
I have one problem with the RFC connection INTEGRATION_DIRECTORY_HMI.
When I test it, SAP ask me in a pop-up window an user/password.
Im sure that SAP shouldnt ask me another user/password like I fill it (XIISUSER) in the definition of the RFC destination.
Coul someone help me ?
Thanks in advance

Hi,
this problem are strang. I also have this problem with my
test installation. Even when i try the trick from Lui it
doesn't work in my case. The popup screen still appeare.
I futhermore have problem with the abap cache refresh in
full mode where i describe in another topic. I would also
interested how to get rid of this problem.
For Martial:
did you install a new XI-System with NW04-SR1 on windows
e.g. windows 2000 Server? Did you have also the cache problem on the abap side?
regards,
Ly-Na Phu
Message was edited by: Ly-Na Phu

INTEGRATION_DIRECTORY_HMI rfc returning error 403

Dear Experts,
I have installed SAP Netweaver 7.4 PI server on windows and MS sql 2012.
i have below issues which i could not get proper solution
1)RFC INTEGRATION_DIRECTORY_HMI returning error as 403: forbidden . This RFC is pointing to /dir/CacheRefresh
2)while creating demo scenarios in Advance adapter engine the file location is showing "/", i tried putting some different directory but getting error as "directory does not exist" so can you tell me which is a default directory for same and in which parameter we can change it.
3)In advance adapter engine some of components are not working and showing in red. what to do in that case
4) I am using Java 6 for opening ESB but it is taking long time and second time it is not opening without restart.
Warm Regards,
Sumit

Hi Sumit,
Please see the below link. Seems to be the same issue.
INTEGRATION_DIRECTORY_HMI 403 Forbidden
Regards,
Jannus Botha

Error when testing INTEGRATION_DIRECTORY_HMI rfc port

hi friends,
I have created a RFC port of type HTTP INTEGRATION_DIRECTORY_HMI it was working fine tillyesterday..
All of a sudden 2day when i am executing the proxy i got error. when i check the rfc is not working.. and giving this error ..
ICM_HTTP_CONNECTION_FAILED
Please suggest me what can i do for that..
Regards
Vijay

hi
In my case all the four rfcs
INTEGRATION_DIRECTORY_HMI
2.        SAPISU_XID
3.        LCRSAPRFC
4.        SAPSLDAPI
are working fine..
and now sproxy is not working now ..
Repository Version   UNKNOWN
when i check =>Check/maintain with report SPROX_CHECK_IFR_ADDRESS
i am geeting this error.
Regards
Vijay

Error in INTEGRATION_DIRECTORY_HMI and CACHE REFRESH

Hi guys, well after checking the forum and several blogs i can't get rid of my problem!
I have a problem concerning INTEGRATION_DIRECTORY_HMI and CACHE REFRESH.
i wanted to get a file from a FTP-Server via CC and i got error:
<SAP:AdditionalText>Error when reading HTTP destination: INTEGRATION_DIRECTORY_HMI.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Because of this i tried to update my cache (SXI_CACHE). When i do a Delta Cache Refresh i get:
Prefix Number: entry missing for system SSID client 100.
When i do a complete Cache Refresh nothing happens at all. I also checked the cache notification in IB - Integration Directory where i fin dout that only the Integration Server (ABAP Cache) won't refresh. Well status is started but nothing else is happening.
Then i checked the RFC INTEGRATION_DIRECTORY_HMI, did a connection test where i get an Internal Server error.
Let me tell u that the systems runs very well in the last days but now i have no clue what might be wrong.
Can somebody please advice me? I already read all blogs concerning this and also did a complete system-restart....
br Jens

when you check INTEGRATION_DIRECTORY_HMI with SM59 it is normal to get
HTTP Response 500 - Internal Server Error. In this case it meens everything OK
see the rediness check, that is attached to SAP note 817920
when you start the complete cache refresh, you can see
the function module SAI_CACHE3_REFRESH_BACKGROUND in SM58. As long as you can see this entry, the cache
refresh is ongoing. If the refresh takes too long and runs on an error, try to specify another timeout in INTEGRATION_DIRECTORY_HMI or in the ICM
Best Regards
Alexander
Message was edited by:
 Alexander Wrobel
Message was edited by:
 Alexander Wrobel
Message was edited by:
 Alexander Wrobel

INTEGRATION_DIRECTORY_HMI Issue

Hi Experts-Can any body tell me what is the use of this RFC INTEGRATION_DIRECTORY_HMI it is showing internal server for me.Can any body reply to me.
Regards
Madhu

Hello
This is a very basic question which could easily be answered by searching on the forum, on help.sap.com or even google.
This thread will be locked by a moderator.
Regards
Moderator

Index or dir/start/index.jsp, PING service and RFC HTTP failing

Hello Experts,
We upgraded our PI system to SAP PI 7.11 SP3 and then implemented SAP notes 1401097 and 1388864.
From then,
any URL http://<FQDN>:5xx00/index.html,
http://<FQDN>:5xx00/dir/start/index.jsp..... are not working.
JAVA is up and running fine.
On ABAP side, PING and RFC INTEGRATION_DIRECTORY_HMI are also not working.
I checked all users and connections (SLD) are working fine.
Kindly help me on this.
Thanks & Regards,
Ananda Swaroop

A common problem. A stop- and start of PI should do the trick (at least it worked for me two times)

PI 7.11 Central Adapter Engine is not started

Hi Experts,
After active objects list, in the central adapter engine: ache update not yet started.
Looking for this error, is possible that is the RFC INTEGRATION_DIRECTORY_HMI because responde 403 forbidden,
Did you have any tips?
Thank you!
Bruno

Are you sure supplied credentials are valid for PIISUSER?
1) HTTP response does not contain a valid XML root tag or Error 'HTTP status code 400 Bad Request' while executing HTTP request (calling method 'get_status')
The error 'HTTP response does not contain a valid XML root tag' occurs when path prefix of the destination is '/dir/hmi_cache_refresh_service/ext'.
The error 'Error 'HTTP status code 400 Bad Request' while executing HTTP request (calling method 'get_status')' when path prefix is '/dir/CacheRefresh'.
Solution: Go to transaction sm59 and open destination of type 'H' INTEGRATION_DIRECTORY_HMI. Select "Connection Test". The connection test should return HTTP response 200.
Now go to "Logon & Security" tab and ensure that username and password are stored in the system. Fixing credentials should fix the problem.
Note: Credentials cannot be tested via "Connection Test" tool. If used credentials are wrong, the server simply returns login html page (using HTTP response code 200). As the login html page is not a valid cache refresh xml document, an error is shown in sxi_cache.

Cache update not yet started In PI 7.1

Hi
Iu2019m using PI 7.1, facing the issue with Cache Update
Under Integration Builder -> Environment -> Cache Notifications
Central Adapter Engine, Mapping Runtime Cache (Central Adapter Engine) both are in gray color status (Cache update not yet started) .
Cache Connectivity Test in RWB
RWB -->Component Monitoring --> Cache Connectivity Test
For both Central Adapter Engine, Mapping Runtime Cache on Central Adapter Engine
Showing the warning
      "--Attempt to fetch cache data from Integration Directory not yet started or still in process"_
Please help me out to update the Cache successfully
Thanks
Vadde

Hi Sekher
Thank you very much for your time,
1 RFC- INTEGRATION_DIRECTORY_HMI is working fine.
2. I du2019t find the com.sap.aii.af.cpa.svc service in NWA ,
3 Under Config Tool
    template - Usage_Type_All_in_One - Services - com.sap.aii.af.cpa.svc
   "CacheType" has the value "DIRECTORYu201D only
Thanks
Vadde

File-Proxy (Error while receiving by HTTP )

Hi All,
I have a problem in the scenario file to Proxy....which is that after placing a source file successfuly in the source directory.... it is showing an information message in the XML message monitoring(sxmb_moni) like below
Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)
Could anybody explain the problem please????where i need to configure to reslove this.
Thanks.
Respond me Imme pls.

First thing to check is that the adapter_plain service is activated in the transaction SICF. (path: default_host-> sap -> xi -> adapter_plain
Then check that the http service is running properly (transaction SMICM).
Also, unless you are connecting to an SAP webAS, you should give a username and password, rather than "Use Logon data fotr SAP System". You could also maintain the URL and authentication data as an sm59 destination and use that in the adapter.
Please look at these...
INTEGRATION_DIRECTORY_HMI: Connection fails
ICM_HTTP_CONNECTION_FAILED
SAF - ICM_HTTP_CONNECTION_FAILED
HTTP adapter setup
Check out this SAP Note- 824554
Also this links
ICM_HTTP_CONNECTION_FAILED
Cache Refresh~
https://websmp201.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
ICM_HTTP_CONNECTION_FAILED ERROR
error code: 400, error text: ICM_HTTP_CONNECTION_FAILED
Error With ABAP Client proxy
Message not reaching Integration server
HTTP content sever - error?
Error in content server configuration
HTTP Client : Code 110 reason
RFC: INTEGRATION_DIRECTORY_HMI
Content server config - error?
Thanks
Swarup

Java components of XI, post installation check

Hey Guys,
I have installed Netweaver 2004s PI along with the Java and ABAP stack, with the ABAP user management pointing to the ABAP stack. I selected the PI option during the installation.
I wanted to know what java components get installed after a successful PI installation. I do not see any particular component related to XI/PI there. I feel the Java Components related to XI have not been installed during my installation. I found this problem during setup step of configuring RFC INTEGRATION_DIRECTORY_HMI. During the test of this HTTP destination the URL gave a 404 resource not found exception.
You can find out the components by using the link
http://<Server>:<Port>/sap/monitoring/ComponentInfo.
The components that are currently installed on my machine are SAP-JEE CAF JLOGVIEW SAP-JEECOR BASETABLES SAP_JTECHF SAP_JTECHS KM-KW_JIKS CORE-TOOLS UMEADMIN JSPM LM-TOOLS ADSSAP BI_MMR BI_UDI CAF-UM .
Is this a common problem during the PI/XI installation.
Please let me know.
Best Wishes
Sumit.

Hello,
Please check the folowing SAP Note for the problem during post-instalaltion activity..u have to set time value for that HTTP RFC..
Note 782801 - SAP Exchange Infrastructure 3.0 SR1 Installation
Note 495857 - Tool: Testing HTTP connection for URL
The most important is that u must have same patch level for all the ABAP + JAVA compoenent to work properly.
plz. dont forget to reward the points

Channels not found

RFC: INTEGRATION_DIRECTORY_HMI working fine. SLDCHECK works fine.
AI_RUNTIME_JCOSERVER, AI_DIRECTORY_JCOSERVER, LCRSAPRFC,SAPSLDAPI, all works fine. CACHE works fine.
But still Communication channels are not found.
No clue where to start dig.

hi
Check this
1 Scenario
This guide deals with all the configurations required to create an IDoc adapter in Exchange Infrastructure
3.0 to send an IDoc from XI to the SAP backend system.
Unlike other types of adapters, the IDoc adapter has dependencies on the XI 3.0 ABAP configurations and
the backend SAP system configurations. Those configurations information will have to be either created
first or retrieved in order to complete the IDoc adapter configuration.
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
     The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
     The Client must be the client number of the backend SAP system.
     Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
     Double-click on the business system in the Integration Directory.
     Switch to Edit mode.
     Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
     The RFC Destination is from step 3.1.
     The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Regards
Hemant
Award points if find helpful

Integration Builder - runtime data cache - Error when creating cache list

All,
When I go into the Integration Builder --> Administration --> Runtime tab --> Data Cache
I get a message saying "Error when creating cache list".
All cache areas look ok and I do not see any other error.
Also, RFC INTEGRATION_DIRECTORY_HMI looks good.
Please advise.
Thanks a lot.

Hi,
Use transaction SXI_CACHE to update the Integration Directory cache. Alternatively, you can use the following URLs to update the CPA cache. Use XIDIRUSER to refresh the cache.
For complete cache refresh u2013 http://<hostname>:<port>/CPACache/refresh?mode=full
For delta cache refresh u2013 http://<hostname>:<port>/CPACache/refresh?mode=delta
If this does not solve the issue, check transaction SLDCHECK to ensure that connection to SLD is available. If the connection fails, check the configuration in the transaction SLDAPICUST. Make sure that the password maintained is correct and the maintained service user is not locked.
Now in the Integration Repository go to Environment u2192 Clear SLD Data Cache. Also go to Integration Directoy and clear the cache using menu Environment u2192 Clear SLD Data Cache.
Open the XI Start Page and click on Administration. On the Repository tab, choose Cache Overview. Refresh the cache using the buttons/icons on the right. Use XIDIRUSER to refresh the cache. Carry out cache refresh in the same way on the Directory and Runtime tabs.
regards,
ganesh.

An error occurred when refreshing the XI runtime cache

i did what is written in note 764176 but to no avail.
t-code sxi_cache shows
unable to refresh cache contents
error during chache refresh.
when double clicking this error
error category is blank.
error id is update.
can anyone help me with this please.

Hi Sas ya,
you can check this link.
problem with xi cache
or try this
Check the RFC Destination
INTEGRATION_DIRECTORY_HMI
After deleting this destination an create it again
everything work fine. This step is very errornous. Take care not to hit the enter key when specifying the user
and password.
Do exactly the same step as describe in the Installation
guide. The hint that it will not works is when you test
the connection and the system prompt you for user and
password again even if you have specified this data
already. In this case you do it wrong. Delete the RFC-
Destination an create it again and again until the test will not prompt you for user and password again!
In the xi "installation guide" you can find section:
"Creating RFC Destinations in the ABAP Environment"
rfc:INTEGRATION_DIRECTORY_HMI
take a look at tab:
Tab: Security/Logon
and text:
Save your entry now, before you switch to next tab, otherwise your entries may be lost.
if you're sure that is was done in a proper way (click by click) no need for change but only if you're sure:)
Select Basic Authentication Confirm both the popup and the warning.
As logon data enter the client of your SAP XI system and the user XIISUSER with the valid password
Save your entry now, before you switch to next tab, otherwise your entries may be lost. Press Enter to go to the next screen.
Or You can follow the links to solve your problem.
Re: SXI_CACHE fails to refresh
Re: SXI_CACHE in ABAP with ERROR
Hope this helps.
Regards,
Vijay

RFC: INTEGRATION_DIRECTORY_HMI

Similar Messages

Maybe you are looking for