Message Interface does not exist in IR u0096 but it does!

Question

Hi, well again i have a problem. I am still trying to get the XI-demo Checkflight…. to run but there are some obstacles on my way.
I just wanted to check a MI given in the ID to check the attributes and picked it in the ID to get linked to the IR but a pop-up appears saying
“Message Interface does not exists in Integration Repository”
What’s the reason for this because obviously it is there, still existing.
I tried to refresh the cache of all XI-components, did a server restart but nothing seems to be working.
On the other hand I have some other questions:
-     Why is it not possible to delete an object (business system) from the ID? I know because of the dependencies of the different channels but it should be possible because of re-generation of the communication-channels (this was also my approach for solving the problem mentioned above!)
-     When do I have to refresh the cache in general? Is it indefinite whenever I want to or it seems to be the right time because something is not running the way it should and it seems a little odd

Answer 1

Hi Carsten Heinrich,
This will help you,
1)     Cache Connectivity Test
In RWB component monitoring, we now have the option of checking whether the cache-connectivity is functioning correctly. This is useful when we are experiencing problems when updating the runtime cache. The system displays a separate window in which we perform the test. If no previous tests have been performed, the system displays a corresponding message. Otherwise, the system shows when and by whom the last test run was started, together with the result of this test.
  To start a new test run, choose Start Test.
The system displays the first results of the test run. Since the whole test takes some time, we can update the displayed results if necessary.
To Update the displayed results, choose Refresh Display.
The overall result for each component is displayed as a green, yellow, red, or gray symbol. A green symbol is only displayed if both update steps for the runtime cache were successful, that is, they both have a green symbol.
2)     Cache notification status
a)     Start the Integration Repository.
b)     Select Environment ® Cache notification.
c)   Have a look at the entries for the relevant user and date.
d)   Have a look at the entries for the relevant cache instance, user and date.
               3)    Cache update and resend the message
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
c)     Call transaction SM58 to check the status of the refresh process.If no entry for function module SAI_CACHE3_REFRESH_BACKROUND is Present any more the cache update is finished.        
         4)     Deleting the SLD Cache
  Many actions require  to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment  ®  Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss