RFC and SSO Configuration

Hi guys,
Is it possible to configure RFC and OSS connection between to sap systems that they are not on the same domain?
Thanks

Hi Reza,
I believe it should work. Pls check this also;
http://help.sap.com/saphelp_nw04/helpdata/en/b8/9ba340fa432b54e10000000a1550b0/content.htm
Thanks and Regards,
Shyam.

Similar Messages

Oid and sso configuration in ebs

Hi,
how to configure the sso and oid for EBS.i red the metalink id 261914.1.i could n't able to understand.
Os : red hat 4.2
application server10.1.2: oraapps.yantro.com
ebs suite 11.5.10 :ebs.yantro.com
how to achieve that
and also we need portal and discover.
please help me out that.

Hi,
how to achieve thatYou will have to install Oracle Applications Server as per (Note: 233436.1) then do the integration part as per the document attached in the note.
and also we need portal and discover.Both are optional.
Regards,
Hussein

Oracle9iAS R2 - Virtual Hosts with Portal and SSO with OIDDAS application

Hi!
I have installed a the machine with name minsk.discover.local. The machine have installed Infrastructure and Portal. The instalation is sucessfull and i work fine. But i have publish Portal to WEB with name intranet.discover.com.br. The Oracle describe:
1 - Create the virtual hosts in SSO and PORTAL - OK
2 - run ptlasst to create SSO Partners Applications - OK
After this steps iwork fine with Portal and SSO, but when i click in portlet to create user to access the application OIDDAS, the Portal redirect to login page of SSO in address mct.com.br, the internal name, when then name not responde in the internet.
I need a help!!!!
Marcio Mesti

I just spoke to the Oracle App server admins, the two servers in question are clustered.
So my question changes slightly to:
What is the best way to install and configure a webgate for clustered Oracle App servers with mulitple virtual hosts, that are residing behind a load balancer (Traffic Manager)?
Thanks,
Andy

SSO Configuration for HWC applications

How to Configure SSO for HWC applications? we are configuring HTTP Authentication in SCC for Single SignOn but not been successful. Debugging the issue we found that MYSAPSSO2 cookie is not being returned.and SSO is not configured in SAP .
How to enable SSO in HWC apps.
What are the Other options to ask password in HWC apps( adding additional Security Layers)

Kunal raman
You/BASIS admin can check in that particular SAP system.
Go to Transacation RZ10
Select Instance Profile as shown in the below diagram
3
3 .Click on Display
4. Then you can see parameter name and its value as below
Rgrds,
Jitendra

Unable to view BI Publisher report with SSO configuration enabled

Hi All,
Can anybody let us know the configuration of the BI publisher with SSO enabled. We are unable to see any of the BI Publisher reports. without SSO configuration we have integration working perfectly fine with the OBIEE and Publisher.
We followed the configuration steps to integrate BI Publisher with Oracle SSO. The following are the steps:
1. deploy analytics.ear as a new application 'analyticsSOAP' in OAS
2. protect analyticsSOAP in mod_osso.conf file under OAS
3. change OBIEE Presentation services configuration to use analyticsSOAP/saw.dll
4. run credstore utility to encrypt password
5.restart xmlp server
6.restart http server
7.restart obiee server
8. restart obiee presentation service
Still we have issues when we try to accesses BI Publisher reports by clicking more Products -> BI Publisher or view reports directly on the OBIEE Dashboard
Thanks in advance.

configure one more virtual path which is unprotected from site minder. we had similar issue for Marketing and resolved by this virtual path.
ref:
http://vaandun-analytics.blogspot.com/2009/11/obi-publisher-with-empty-obi-catalog.html
Thanks
Sarathi

File to RFC, and through RFC response i am trying to trigger the Mail adapt

Hi All,
Right now i am doing File to RFC, its working fine but now the requirement is when xi connect to ftp and picks the file need to send one success mail after the file pickup and data sent to BW system again i need to send one mail and also error alerts to inbox.
Till now i am not using BPM, can we do this without BPM pls let me know
now i am trying to achieve this in File to RFC, and through RFC response i am trying to trigger the Mail adapter.
or else i need use only BPM pls share the steps which i need to be configure.
Am i correct or pls suggest me some idea to achive this and also pls share some smaple ones in BPM .
Thanks in advance
Venkat

With BPm, follow this:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Instead of receiving the response in file, use mail adapter
Regards,
Prateek

SSO Configuration in UNIX Environment

Hi,
We are planning to impliment SSO between 2004s Portal with R/3, BW, and host of other non SAP application which supports SSO. All the applications are hosted in UNIX environment.
Could anyone help us in understanding the pros and cons of having SSO in unix envrionment. Also you could give us any document (other than help.sap.com) which guides us in configuring will be of great help.
Thanks
Vivek Raj.

Hi,
There are no pros and cons for <b>SSO on Unix</b>. Needless to mention, the pros and cons of different operating systems supported by SAP.
The steps involved to configure SSO remains the same for any of the SAP backend systems:
1) Create a system on Portal and give a system alias to it.
2) Download the verify.der file from Portal (System Administration -> System Configuration -> Keystore Administration)
3) Log on to the backend SAP system.
4) Use transaction STRUSTSSO2 and import the Portal certifcate (verify.der) to the SAP R3 or SAP BW or SAP CRM or for that matter any SAP system with ABAP stack.
5) Give the values for EP system ID, client and language. Refer to this link : http://help.sap.com/saphelp_nw2004s/helpdata/en/78/f1a8490e7011d6999500508b6b8a93/content.htm
6) Configure the backend SAP systems to accept and verify the logon ticket. Use RZ10 and set the parameters : login/accept_sso2_ticket=1 and login/create_sso2_ticket=1
7) Restart your R3 or BW system.
For non-SAP systems, can you just let me know which systems are you referring to ?
Incase you need a document for SSO configuration, do send me your email address. You can also find documents in SDN Library.
Regards,
Sunil

What is adaptive RFC and How to Use it

hi friends
what is the adaptive RFC
what is the use of it
how we can use it
explain me anyone
and send pdf also
thanks
ramu.

Hi,
To give u a brief idea.
rfcs are used to call data from the backend that is R/3.We use the Bapis from the R/3 system which have some pre defined functionality and data is populated in the correspoding ui elements in webdynpro interface.earlier Rfcs were used but now we have adaptive rfcs in which
if there are changes in the backend(R/3 system) such as changes in the datatype,structures,fields would be automatically be refllected in the rfcs and there would be no errors in web dyn pro even if there is a change in the back end
to be more specific folow this link
http://help.sap.com/saphelp_nw70/helpdata/EN/41/38bc8f813719488ddc9d9b21251ec3/frameset.htm
and try out this application
to use the rfcs firstly check out this document for configurations
Important Configurations for Calling ABAP Function from Java Web Dynpro Application
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07753b9-fa0c-2a10-64a8-c6754c45396e
heres the application.
Creating a Web Dynpro Application Accessing ABAP Functions
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/355b9c90-0201-0010-d2a8-89fece426526
regards
Nikhil Tapkir

SAP CRM to ECC - SSO Configuration - Logon Language Setup

Hi All,
I am a BASIS consultant currently handling one CRM project. I need a help in configuring SSO between CRM and ECC. Now SSO is not configured, so When I click on the External Link created in CRM calling an ECC transaction, it requests for Client/UserID/Password/LogonLang for the ECC system. Here it takes Logon Language as same as what I have logged in CRM. Hope once SSO configured it will check only for the userID and log into ECC without requesting any further details. But the issue here is we are planning to have additional languages in CRM but not in ECC. So whenenver user logs in CRM with language other than EN - english (eg. FR), and when tried to login to ECC with the external link from CRM, by default ECC login needs to be logged in with language EN, as FR will not be available in ECC. I do not find any logon language configuration in SSO, how can we achieve this, logging into language FR in CRM, logging in EN when clicking External ECC link? Configuring Logon Data defaults (in SU01) in ECC, restricting to logon language EN, will not help I hope. Please advise.
Thanks in advance.
Regards,
Shahul

Hi Srikishan,
Thanks for the response. When user from CRM logged in another language than EN for eg. FR, clicks on external link in CRM, takes to EN, only if that language FR is not installed in ECC, else it will take to the same language in which CRM user logged in. This cannot be controlled in SSO configuration. Is this correct?
In case if FR is installed in both the systems, ie CRM and ECC, but user wants to log only to EN when clicked the external link(to ECC) from CRM, how we can configure this, Is any parameter can control or SSO setup configuration available? Please advice.
Regards,
Shahul Hameed

SSO Configuration in BO Platform(CMC) & SAP BW 7.0

HI All,
We are using SAP BO Platform 4.0 SP01 and SAP BW 7.1 and developed few BO WEBI reports on BEX Queries . I want to configure SSO (SINGLE SIGN ON) to enable analysis authorizations of BW. I did all the following steps, but getting OLAP Error when we try to execute query without BO Administrator role.
we configured analysis authorizations in SAP BW and tested. its working fine.
we uploaded key store file into CMC and certificate into SAP BW.
we enabled single sign on at BEX connector in CMC.
Imported roles , users into BO From BW and assigned BO roles like EVERYONE and folder access related roles.
we did settings in BILAUNCHPAD txt file in WEB-INF, CUSTOM folder.
The same settings are done in SAP BO 4.0 SP06 and SSO is working fine and getting the data as per the security given in BW.
Please suggest me if I am missing anything.
Thanks,
Joseph

Hi Mayank,
Unfortunately i cant attach screen shot. Without SSO selection in authentication i am getting output. But when i select SSO in authentication .I am getting below error.
"Cannot connect to OLAP Source (Error:INF).
Regards,
Joseph

Is There any Relation Between PCD and SSO

Hi,
Is there any relation between PCD and SSO, why because if i am try to connect from portal to R/3 in the user mapping i got one error i.e some pcd error.
pls tell me how to rectify that.
Regards,
Jagadish Babu Kanikanti.

Hi Jagadish
The PCD is only a central persistance for storing Portal objects. There is no such relation between PCD and SSO that could create a problem. You can however check for the PCD error in this manner.
1. In the system administration role, choose System Administration -> Support. The Support Desk appears.
2. Select the area Portal Content Directory.
3. Click on PCD Configuration in the test and configuration tools. The next screen shows all the parameter values currently maintained for the PCD.
4. To reload the configuration, choose Reload.
Hope that helped.
Best Regards
Priya

Regarding rfc and idoc sender

hi
   can any one provide me with some scenarios having
idoc and rfc as senders.

Hi
To Configure the RFC to FILE scenario ,Proceed as Follows
a.       Create an RFC Destination to XI in transaction code (SM59)
b.       Create new destination of type T (TCP/IP)
c.       Make sure you select Registered Server Program option before writing your program ID
d.       Write you program ID (remember it's case-sensitive)
e.       In the gateway host and gateway service write the values of your Application system - business system (not the XI server)
             Step2:Repository
1)       From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
         From the list of Software Component Versions, Choose your own software component version .Click Import.
3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
         The namespace is ur:rfctofile
4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
         After this specify the connection parameters to the R/3 system:
4.1)     System IS :sapfox
4.2)     Client IS :800
         Then Save it. The new namespace will be visible under software component version node in the left frame.
         Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3)     Application server:172.25.5.7
4.4)     System number: 00
4.5)     User name:developer
4.6)     Password: Password of Sap R/3 system.
         Then click continue .You will find IDOC and RFC node. Click on this node and select the   Idoc or Rfc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the   Rfc and Idoc will be available into XI as Message types. So no need to create any Rfc or Idoc Structure. We need to create a structure for file only.
5).      Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6)        Create new data types.
6.1)      Right click on Data types and select New.
           Your Data Type is. dt_file
          In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
          Save the object.
6.2)      The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
          no need to create Data types. They are imported directly as Message types.
6.3)      To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
          Select the following.
6.3.1)    Category: XSD.
6.3.2)    Messages: From All Available Global Elements.
6.3.3)    File:
          Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7).      Create a new Message Type.
7.1)     In the left hand frame under Interface objects, right click on the Message types and select new.
7.2)     Give a suitable name to the Message type.(MT_ messagetype).
7.3)     For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
         Save it.
8).     Create a Message interface
8.1)    In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2).   The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
        Save it.
9) .    Create a graphical mapping between the target document and the sender .
9.1)    In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2)    As Source message select your own Message type.You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- >     Namespace->Imported Objects.
9.3)    As Target Message you can choose your Rfc .Choose Search for Integration Object.
9.4)    Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5)    Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
        Save It.
9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10).     Create an Interface Mapping.
10.1)   In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2)   Source interface : Your Outbound Interface (The Source document(Rfc) interface).You can Choose Search for Integration Object.
10.3)   Target interface:    Your Inbound Interface( The Target document interface).
        Then Select 'Read Interface' and Assign your 'Mapping Program' .
        Mapping Program: Your Message mapping.
        Then Save it.
11.)    Finally , in the left hand frame ,go to your change list and Activate it
           STEP 3: Directory
1)      From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
        Create a Scenario Object
2).     The First Step is to create a Scenario Object
        This will serve as container for all your configuration work. Create and save a scenario object
3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4)      In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) .    Create a Communication Channel.
6).     Expand your service and right click on Communication Channel. Name your Communication Channel
        Here we need to configure the adapter.
    Since the Sender is 'RFC', Specify the following Parameters
         For the adapter type , use the F4 help and select RFC.
         Specify Sender since the adapter will be sending messages to XI
         Specify the following parameters.
         Transport Protocol: RFC
         Message Protocol:   RFC(RFC XML )
         Adapter Engine: Integration Server
         Adapter status: Active
         RFC Server Parameter:
         Application Server(Gateway):172.25.5.7
         Application Server Service(Gateway Service): sapgw00
         Program Id: Id of Registered server program ( it is case sensititve)
         And the adapter is configured. Save it
          Since the Receiver is File , Specify the following Parameters
6.1       For the adapter type , use the F4 help and select FILE.
6.2       Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3       Specify the following parameters.
          Transport Protocol: File Transport Protocol.(FTP)
          Message Protocol: File Content Conversion(since the xml files produce by XI need to be converted to text files)
          Adapter Engine: Integration Server
          For the File system access Parameters, enter the following
          Source Directory:Test
          File Name: Input.txt
6.4       For the FTP Connection Parameters, Specify the Following
          Server:172.25.5.240
          Port: 21(by default)
          Data Connection: Passive
          Connection security: None
          Connection Mode: Permanently
          Transfer Mode: Binary
6.5       For Processing Parameters, Specify the following
          File construction mode: Add Time Stamp
          File Type: Binary
6.6       For Content Conversion Parameters, Specify the Following
          RecordSet Structure:
          Adapter Status: Active
          The receiver file adapter is now configured. Save your Communication Channel.
           Create an Receiver Determination.
7).       From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1)      Select your sender service and interface.
          Sender:
          Party: blank
          Service: Sender service(Business system)
          Interface : Sender interface
7.2)      In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
            Create an Interface Determination.
7.3)       Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1)     In the Receiver Determination   you just created, have a look at the area Configuration Overview for Receiver Determination   at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2)     In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
           Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3)     You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
           After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5)     When you are done , Save the Interface determination object.
8.)         Create a Sender Agreement.
           In the left hand frame , right click on Sender Agreement ->New
8.1)       Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Outbound Interface
8.2)       In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.)         Create a Receiver Agreement.
           Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1)       Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2)       In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
           Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Inbound Interface
9.3)       In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
           Your Configuration is complete. Activate the objects.
To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1)   Create an RFC Destination to the Sending System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select create new button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in SAP R/3 towards other system
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Outbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
5)   Create Customer Distribution model in the transaction code BD64
1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3)   Save the Distribution model
    Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
4)   Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> Distribute to the destination client
    Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
             Step2:Repository
1)       From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
         From the list of Software Component Versions, Choose your own software component version .Click Import.
3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
         Your NameSpace is urn:idoctofile
4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
         After this specify the connection parameters to the R/3 system:
4.1)     System :sapfox
4.2)     Client :800
         Then Save it. The new namespace will be visible under software component version node in the left frame.
         Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3)     Application server:172.25.5.7
4.4)     System number:00
4.5)     User name: developer
4.6)     Password: Password of Sap R/3 system.
         Then click continue .You will find IDOC node. Click on this node and select the   Idoc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the    Idoc will be available into XI as Message types. So no need to create any Idoc Structure. We need to create a structure for file only.
5).      Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6)        Create new data types.
6.1)      Right click on Data types and select New.
           Your Data Type is :dt_file
          In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
          Save the object.
6.2)      The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
          no need to create Data types. They are imported directly as Message types.
6.3)      To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
          Select the following.
6.3.1)    Category: XSD.
6.3.2)    Messages: From All Available Global Elements.
6.3.3)    File:
          Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7).      Create a new Message Type.
7.1)     In the left hand frame under Interface objects, right click on the Message types and select new.
7.2)     Give a suitable name to the Message type.(MT_ messagetype).
7.3)     For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
         Save it.
8).     Create a Message interface
8.1)    In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2).   The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
        Save it.
9) .    Create a graphical mapping between the target document and the sender .
9.1)    In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2)    As Source message select your own Idoc .You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- >     Namespace->Imported Objects.
9.3)    As Target Message you can choose your Message type .Choose Search for Integration Object.
9.4)    Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5)    Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
        Save It.
9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10).     Create an Interface Mapping.
10.1)   In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2)   Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose Search for Integration Object.
10.3)   Target interface:    Your Inbound Interface( The Target document interface).
        Then Select 'Read Interface' and Assign your 'Mapping Program' .
        Mapping Program: Your Message mapping.
        Then Save it.
11.)    Finally , in the left hand frame ,go to your change list and Activate it
           STEP 3: Directory
1)      From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
        Create a Scenario Object
2).     The First Step is to create a Scenario Object
        This will serve as container for all your configuration work. Create and save a scenario object
3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4)      In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) .    Create a Communication Channel.
6).     Expand your service and right click on Communication Channel. Name your Communication Channel
        Here we need to configure the adapter.
     Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
          For the Receiver, Specify the following Parameters
6.1       For the adapter type , use the F4 help and select FILE.
6.2       Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3       Specify the following parameters.
          Transport Protocol: File Transport Protocol.(FTP)
          Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
          Adapter Engine: Integration Server
          For the File system access Parameters, enter the following
          Source Directory:Test
          File Name: Input.txt
6.4       For the FTP Connection Parameters, Specify the Following
          Server: 172.25.5.240
          Port: 21(by default)
          Data Connection: Passive
          Connection security: None
          Connection Mode: Permanently
          Transfer Mode: Binary
6.5       For Processing Parameters, Specify the following
          File construction mode: Add Time Stamp
          File Type: Binary
6.6       For Content Conversion Parameters, Specify the Following
          RecordSet Structure:
          Adapter Status: Active
          The receiver file adapter is now configured. Save your Communication Channel.
           Create an Receiver Determination.
7).       From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1)      Select your sender service and interface.
          Sender:
          Party: blank
          Service: Sender service(Business system)
          Interface : Sender interface
7.2)      In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
            Create an Interface Determination.
7.3)       Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1)     In the Receiver Determination   you just created, have a look at the area Configuration Overview for Receiver Determination   at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2)     In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
           Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3)     You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
           After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5)     When you are done , Save the Interface determination object.
8.)         Create a Sender Agreement.
           In the left hand frame , right click on Sender Agreement ->New
8.1)       Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Outbound Interface
8.2)       In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.)         Create a Receiver Agreement.
           Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1)       Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2)       In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
           Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Inbound Interface
9.3)       In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
           Your Configuration is complete. Activate the objects.
plz rewards points
vikas

RFC and IDoc

Hello
Both RFC and Idoc adapters are used to connect to SAP system from XI. Why is that we have to configure RFC Destination, port and partner agreement for Idoc while we do not have to do that for RFC ? Both use the same RFC protocol still we do the configurations only for Idoc. Can someone explain to me the technical reasons why we do that
Thanks
Radhika

Hi,
RFC Adapter resides in Adapter Engine,
IDoc resides in I.E,when you triiger an IDoc it directly Hits I.E,like communication with Other SAP System.
Thats why we need to create the port .....details for IDoc.
But coming i future it IDoc adapter ,HTTP Adapter moving in to JAVA Stack,wait till 2010 july.
in PI7.1 EHP1 there are too many changes in Idoc adapter,like Idoc package we can do at Sender IDoc adapter level.
Regards,
Raj

SAP Best Practices for SSO Configuration

Hello There,
Are there any SAP Best Practices available for SSO Configuration. If so, Kindly help me with those..
And also any Third party tools available in the market for SSO Configuration..
Appriciate your Help on this.. Thanks in advance.
Regards,
Pranay S
Edited by: Pranay Subedari on Apr 29, 2011 9:12 AM

Hello,
Types on the SSO are classified with the systems involved in configuration (i.e.) SSO between ABAP Stack and Java stack or LDAP, OS
Refer the link for more details [Document Deleted]
Regards,
Anand
Message was edited by: Jason Lax

File-RFC-File SLD configuration

Hello everybody!
Currently I'm trying to create a File-RFC-File scenario. So that request from file is send to RFC and after that the RFC response is written to file. I'm following some guides on this topic here on sdn. So I'm almost done with ESB and IB designs but got stuck with SLD configuration. It's pretty confusing to me what software components, business and technical systems should i create for the purpose of my scenario. Could you please explain it step-by-step?
Thanks in advance,
Peter

>>>>>>>>confusing to me what software components, business and technical systems should i create for the purpose of my scenario
You dont need any software component or product is required, since already you are done with those objects.
May be you have used existed sofware component version for creating ESR objects. Okay.
1. You need one business system for R/3 or ECC
2. Juss get into SLD and create Technical System and Business System (If not yet available for R/3 or ECC)
3. As you have completed ur ESR, you can get into Configuration part
4. Choose - Communication component with out party
5. right click and assign business system (if R/3 or ECC is not yet assigned)
6. For File - you can go business service
That's it.
Regards
Pothana

RFC and SSO Configuration

Similar Messages

Maybe you are looking for