Skip to Content
author's profile photo Former Member
Former Member

Doubts in File to RFC scenario

<u><b>Scenario we are working on:</b></u>

Legacy System -> Flat File -> XI2.0 -> RFC -> SAP R/3 470 ( WAS 620 )

<u><b>What we have done till now:</b></u>

1. Created technical system for XI server and the SAP 620 ( target system )

2. Created business system for XI Server and target system

3. Created a software product for legacy system and the corresponding technical system and the business system

4. Defined the business scenario in Repository including Actions, Message Interface, Message Type, Data Type (for source file), Imported RFC signature from target system, message mappings and message interfaces.

5. Configured the file adapter.

6. Configured business scenario in Integration Directory including interface determination and receiver end points

<u><b>Where we are stuck:</b></u>

1. Currently I have created the entire set of objects under the new software component I created for source system. I want to know how to decide under which software component should I create the design objects, e.g under the software component for source system, or under the software component for target system or am I supposed to create a new product altogether including all the software components in my scenario.

2. What is the significance/dependency of namespace in the design process?

3. I have configured the inbound file adapter (attached is the configuration file). How do I integrate it with the Integration server? In other words where to specify the link between my business scenario the file adapter. How do they talk to each other?

4. We are not able to configure the RFC adapter. Can we get a configuration file for a working adapter? Are there any pre-requisites for the RFC adapter configuration? Also once configured how will it talk to Integration Server?

5. Is it possible to use proxies on Integration server in our scenario? Our XI system is installed on WAS 620 with J2EE 620 and the target system is also WAS 620.

6. Is it possible to send email notification from XI in case or any errors e.g while accepting the file, while mapping, or while passing to target system

Add comment
10|10000 characters needed characters exceeded

3 Answers

  • Posted on Jul 29, 2004 at 08:21 PM

    Hi Satinder,

    Below are the answers for your questions:

    Regards

    Prasad

    Netweaver RIG-XI

    SAP Labs LLC.

    Ans1: If you are creating a new sceanrio, you can create a product and a software component in SLD and import the software component into Int.Repository. You can define 1 namespace or mutliple namespaces under this SC.

    It all depends on how are desiging your objects in SLD, Int Rep etc. This can be done in various ways.

    Ans2:

    Namespaces Definition:

    Namespaces in the Integration Builder are namespaces in the sense of XML namespaces that are sub-divided further into semantic units within the Integration Builder software component versions. Objects of a namespace can only be shipped as part of the corresponding software component version and not separately.

    XML Namespace Definition: An XML namespace is a collection of names, identified by a URI reference , which are used in XML documents as element types and attribute names

    RFC2396

    IETF (Internet Engineering Task Force) RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax

    Use

    The following types of namespaces exist in SAP Exchange Infrastructure:

    · Repository namespaces are displayed in the Integration Builder (Design) navigation tree. They are all assigned to a software component version but are used differently:

    ¡ Repository namespaces are used to avoid naming conflicts. For objects of the same object type, it is not possible to have duplicate object names within a repository namespace. In other words, a repository namespace is a quantity in the Integration Repository in which the object names are unique.

    ¡ Software component versions are used to define shipment units. It is not possible to ship objects in a namespace (business scenario objects, business process objects, interface objects, mapping objects, and adapter objects) on their own. Instead, they are shipped as a part of the relevant software component version.

    Although repository namespaces are assigned to the software component version in the navigation tree, the software component version does not affect the uniqueness of the object names.

    · XML namespaces are used as identifiers for message instances or customer-specific fields in the instance. You can specify XML namespaces as an attribute of (fault) message types and data type enhancements.

    · Namespaces in the System Landscape Directory (SLD), which have nothing to do with repository or XML namespaces (see: Namespace).

    · Internal namespaces, which are required in message instances, for example. The internal namespace for fields in the message header is: http://sap.com/exchange/MessageFormat, for example. These namespaces are of no further interest for SAP XI users.

    Ans3: Check the Adpater Documentation. In your case, the legacy system will be creating a file in the file system where the file adpater is installed.You have to mention this path in your FA configuration. Once the FA is running, The file is polled automatically. The parameter defined in the config file will send direct the message to XI server. For Ex:

    XMB.TargetURL=http://:8000/sap/xi/engine?type=entry

    Ans4: Check the documentation for RFC Adapter Config. Once configured it will talk to XI via JCO. send me an email if you have more questions.

    Ans5: Yes you can use Proxies as your target system is was620.

    Ans6: this is possible in XI-3.0 -SP04 as the SMTP adpater is available. You have to model the message in XI-3.0 when to send an email message.

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 30, 2004 at 02:31 PM

    Hi Prasad thanks for the reply.

    3. I am still having issues with my file adapter. I have configured as mentioned in the guide and it comes up also then in the log when I check it just get stuck at this message that

    (4062): Sending text message "7b1a4441-cdc5-11d8-bba9-f580ac19a488" type "text/plain" to Integration Engine... (message size: 150 bytes, URL: "http://punhjwsapxi:8000/sap/xi/engine?type=entry")

    After that nothing happens and I can't even stop the file adapter. I have to restart the adapter engine.

    Are there any prerequisite, any service required to be running before I start my file adapter, any pipelines to be started, queues to be onfigured ???

    4) In RFC adapter as of now I am only interested in outbound scenario. Still do I have to cinfigure everything or I can skip the source system part ?

    Error I am getting currently is

    (6030): Attempt to start RFC adapter failed: com/sap/mw/jco/JCO$Record

    5) Some documentation says that one have to have J2EE 630 or higher to use proxies !!!

    Thanks in Advance

    Satinder

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 30, 2004 at 06:32 PM

    Update:

    Also just now I checked that even when I give the following URL in Web browser, it just hangs with no response.

    http://<host>:8000/sap/xi/engine?type=receiver

    Any clues why ?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Satinder,

      I'm assuming that <host> in the URL is replaced with the actual host value (eg: 1.2.3.4 or abcxid).

      Secondly, check if the port 8000 is configured & open. Usually its 8200.

      Let me know.

      Homiar.