Agrees with all that Mike says
Q1) Common error here during connection test is "program not registered". As Mike said do not
try to register this manually in Netweaver. This is an automated process. Please follow the steps
below that will register the program (will be available in soon to be released SAP note 1528512)
For the MII delivered idoc listener resource adapters it is not required
to follow the steps from note 353597 ie. rfcexec should
not be used to register the server program.
Follow the steps below to help resolve this issue,
1) Navigate to the resource adapter in the netweaver administrator
NWA -> Configuration -> Infrastructure -> Application resources
2) Find the XMIIIDOC0* adapter, note down all of the values
and save them for reference.
Please initialise all fields except for the fields below which
should keep these values-
MaxReaderThreadCount 0
Language EN
BindingKey XMIIIDOC
3) Save the initialised adapter
4) Restart the resource-
NWA -> Operation Management -> System -> Start and Stop
Page 2
-> Java EE applications -> Enter idoc to search and find the
relevant application
5) Select and choose Start -> On All instances
6) Return to the resource adapter initialised in step 2 and
fill in the data again. When this is saved with valid data
the server program you enter in the corresponding field
will be registered on the gateway automatically. This can be
any name but must correspond exactly to what is defined in SM59.
>> Note, make sure to set MaxReaderThreadCount >= 1
Any incorrect config will cause the resource to stop. To check
if a resource has stopped you must refresh the browser page (F5)
and find the resource again. It can be misleading as
a resource adapter may show as green status until the page refresh
If a resource stops it must be initialised saved and
started again (repeat steps 1-5)
Second common error is what Mike Mentioned, changes to the resources can lead to the MII
message listener configuration being initialised. An update from the MII Listener Config should resolve
the more common RFC_ERROR_SYSTEM_FAILURE errors.
Q2) Same as Mike's response, duplicated program ID's should not be used.
Q3) There is a Metadata cache in Netweaver and the only reliable way to clear this
is to restart netweaver. This step is normally only required if you change the
Metadata definition on the ECC side and need this updated.
METADATA_UNAVAILABLE errors are always either authorisation or
incorrect definition of the segments in ECC. IDOC_READ_COMPLETE
can help to identify both. Testing from both ECC and MII can help identify
where problems exist. This function module is what is used via RFC
by external applications to retrieve the Idoc MetaData.
If the error raised includes information like
IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type u201CXXX u201D with extension u201CYYYu201D is unavailable.
In this case it can be that the definition itself in ECC is a problem, be sure to include the
extension information when passing to IDOCTYPE_READ_COMPLETE for troubleshooting. It can also be worthwhile
to test a non-modified or extended message type to eliminate the possibility of this problem and ensure authorisations
or resource configuration are not the problem.
Edited by: Eoin Donnelly on Jun 3, 2011 12:27 PM
Edited by: Eoin Donnelly on Jun 3, 2011 12:31 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.