** Unable to see message interfaces in ID under Business Systems
Hi Friends,
When I create sender / receiver agreement in ID by choosing the respective Business Systems I am not able to see my message interfaces. Then, I checked the SLD, our SWCV under Products are not assigned in the Business Systems.
Then, I have assigned our SWCV (by selecting the product, be selecting the SWCV) in tehcnical system and business systems, saved and log off from SLD.
But, still those message interfaces are not appeared while select the Business systems. Those interfaces are abstract interfaces. I tried to close the IR and ID, open it again, still the same problem.
What could be the reason ? Reply friends,
Thanking you
Jegathees P.
Hi,
a new import of the Business System is not necessary.
1) Important is to activate the interface in the Integration Repository.
2) Checking in SLD that all installed check boxes are selected. In the Business System -> Installed Software -> select the Product and check that the SC is selected.
In IR it's enough to close the Business System and reopen it to see the new interfaces.
Regards
Patrick
Similar Messages
-
CcBPM - How to use 1 Message Interface for 2 different Business System
Hi,
I have this bpm scenario below :
JDBC QUERY (ASYN) ---> RFC (SYNC) -
> JDBC INSERT (ASYN) -
> MAIL (ASYN).
So Both JDBC INSERT and MAIL using the same data input from RFC response for instance i will named as MI_RFC_RES_ASYN_ABS. I have problem to configure in the integration directory, how make the xi smart enough to routing in the correct business system.
JDBC -
> BS_JDBC and MAIL -
> BS_MAIL base on the send step in BPM because the interface is the same.
Cheers
FernandHi,
If you want to send the same mesg to diff systems and also need to have the control on seq,
then define 2 diff abstract interfaces for messages going out of BPM (with same message type so that structure is same).
One will be used to define send step for JDBC and other for BPM.
Define 2 send steps in BPM one for JDBC and other for mail using these abstract interfaces.
Now you will have 2 receiver determinations.
Since recr is determined based on sender system interface name and name space,
system name ( BPM ) and name space will be same for both the messages going out of BPM.
for JDBC abstract interface BS_JDBC will be recvr.
and for Mail abstract interface BS_MAIL will be your receiver.
hope it answers your qn.
Regards
Pushkar -
I am unable to see a newly added PC under devices in SCCM2012R2 console
Hi,
I am unable to see a newly added PC under devices in SCCM2012R2 console. Plz help me how to add a system to SCCM2012R2 consoleWhere and how have you added computers? Computers are added when the ConfigMgr client is installed or by a discovery method.
Torsten Meringer | http://www.mssccmfaq.de -
HT4623 I am unable to see the software update link under settings.please help
I am unable to see the software update link under settings.please help
Unless you are already using iOS 5, you have to connect to your itunes (on your computer) by cable, and will not have the update option in your iPhone's settings.
-
Unable to see DB13 and ST04 logs in the system.
Hi All,
We are unable to see the DB13 logs in our SAP system. The same is happening while trying to look into the ST04 logs for Database Message Logs. In both the cases we find the same kind of log:
[in DB13 log]************************************************************************
BR252E Function fopen() failed for '/sapdba/sapcheck/cdvxzfrv.aly' at location file_printout-1
BR253E errno 2: No such file or directory
External program terminated with exit code 5
[in ST04 log]*************************************************************************
BR252E Function fopen() failed for '/sapdba/saptrace/background/alert_PIN.log' at location file_printout-1
BR253E errno 2: No such file or directory
External program terminated with exit code 5
SAP is running on Varitas cluster on two different nodes. One node is having SAP services and the another one Oracle services on it. Since the last week when we shifted the Oracle services from one node to another for monthly maintenace work, we are facing this problem.
Our system details are:
SAP 46C (kernel 46D_EXT) 32 bit
SuSe Linux 2.6.5-7 64 bit
Oracle 9.2.0.6.0
Can someone please help me on it.
AnilThanks Padmaja/Eric for your reply !!!
File systems are properly mounted and I can see these said files at OS level. Following are the env variable:
USER=dinadm
LOGNAME=dinadm
HOME=/home/dinadm
PATH=/oracle/DIN/920_64/bin:.:/home/dinadm:/usr/sap/DIN/SYS/exe/run:/opt/kde3/bin:/opt/gnome/bin:/usr/games:/home/dinadm/bin:/usr/bin/X11:/usr/bin:/bin:/usr/sbin:/sbin:/usr/lib/java/jre/bin
MAIL=/var/mail/dinadm
SHELL=/bin/tcsh
SSH_CLIENT=10.234.14.33 1364 22
SSH_CONNECTION=10.234.14.33 1364 10.234.13.50 22
SSH_TTY=/dev/pts/0
TERM=xterm
HOSTTYPE=x86_64-linux
VENDOR=suse
OSTYPE=linux
MACHTYPE=x86_64
SHLVL=1
PWD=/usr/sap/trans/data
GROUP=sapsys
HOST=insapr3din01
HOSTNAME=insapr3din01.pdc.in.ap.holcim.net
MANPATH=/usr/share/man:/usr/X11R6/man:/usr/local/man:/opt/gnome/share/man
MINICOM=-c on
INFODIR=/usr/local/info:/usr/share/info:/usr/info
INFOPATH=/usr/local:/opt/gnome:/usr
LESS=-M -I
LESSOPEN=lessopen.sh %s
LESSCLOSE=lessclose.sh %s %s
LESSKEY=/etc/lesskey.bin
PAGER=/usr/bin/less
MORE=-sl
GZIP=-9
CSHEDIT=emacs
COLORTERM=1
NNTPSERVER=news
XFILESEARCHPATH=/usr/lib/X11/%L/%T/%N%C:/usr/lib/X11/%l/%T/%N%C:/usr/lib/X11/%T/%N%C:/usr/lib/X11/%L/%T/%N:/usr/lib/X11/%l/%T/%N:/usr/lib/X11/%T/%N:/var/X11R6/%T/%N%C:/var/X11R6/%T/%N
INPUTRC=/etc/inputrc
LANG=en_US.UTF-8
QTDIR=/usr/lib/qt3
no_proxy=localhost
WINDOWMANAGER=/usr/X11R6/bin/kde
JAVA_BINDIR=/usr/lib/java/jre/bin
JAVA_ROOT=/usr/lib/java
JAVA_HOME=/usr/lib/java/jre
JRE_HOME=/usr/lib/java/jre
CVS_RSH=ssh
G_BROKEN_FILENAMES=1
GNOME_PATH=/opt/gnome:/usr
GNOMEDIR=/opt/gnome
ACLOCAL_PATH=/opt/gnome/share/aclocal
PKG_CONFIG_PATH=/opt/gnome/lib/pkgconfig
GTK_PATH=/usr/local/lib64/gtk-2.0:/opt/gnome/lib64/gtk-2.0:/usr/lib64/gtk-2.0
MODULE_VERSION=3.1.6
MODULE_VERSION_STACK=3.1.6
MODULESHOME=/usr/share/modules
MODULEPATH=/usr/share/modules/versions:/usr/share/modules/modulefiles
LOADEDMODULES=
CSHRCREAD=true
LS_OPTIONS=-N --color=tty -T 0
SAPSYSTEMNAME=DIN
DIR_LIBRARY=/usr/sap/DIN/SYS/exe/run
LD_LIBRARY_PATH=/usr/sap/DIN/SYS/exe/run:/oracle/client/92x_32/lib
THREAD=NOPS
dbms_type=ORA
dbs_ora_tnsname=DIN
dbs_ora_schema=SAPR3
ORACLE_PSRV=DIN
ORACLE_SID=DIN
ORACLE_HOME=/oracle/DIN/920_64
ORACLE_BASE=/oracle
ORA_NLS=/oracle/DIN/920_64/ocommon/NLS_723/admin/data
ORA_NLS32=/oracle/DIN/920_64/ocommon/NLS_733/admin/data
ORA_NLS33=/oracle/client/92x_32/ocommon/nls/admin/data
NLS_LANG=AMERICAN_AMERICA.WE8DEC
SAPDATA_HOME=/sapdata/oracle/DIN
waiting for your reply,
Anil -
Unable to see Messages in External Definitions
I imported the WSDL below and created a Message Interface based on JobSubmitRequest but, when I come to map to it, all I see in the tree structure is node 'JobSubmitRequest' with elements 'parameter' and 'request_header'.
I also cannot see any messages in External Definitions.
Can anyone help with a solution?
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xoa="http://xoa.xpedite.com/2004/11/xoa" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xoa.xpedite.com/2004/11/xoa">
<types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://xoa.xpedite.com/2004/11/xoa" xmlns="http://xoa.xpedite.com/2004/11/xoa">
<!-- address type enum -->
<xs:simpleType name="AddressType">
<xs:restriction base="xs:string">
<xs:enumeration value="fax"/>
<xs:enumeration value="internet"/>
<xs:enumeration value="mbox"/>
<xs:enumeration value="x400"/>
<xs:enumeration value="telex"/>
<xs:enumeration value="cablegram"/>
<xs:enumeration value="mailgram"/>
<xs:enumeration value="ddd"/>
<xs:enumeration value="dedLine"/>
<xs:enumeration value="softswitch"/>
<xs:enumeration value="voice"/>
<xs:enumeration value="sms"/>
<xs:enumeration value="fod"/>
<xs:enumeration value="list"/>
<xs:enumeration value="smQuery"/>
</xs:restriction>
</xs:simpleType>
<!--includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="AuthenticateRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="Domain" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- The authenticate result (used to send back results for synchronous and asynchronous requests) -->
<xs:element name="AuthenticateResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSCreateDirRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSCreateDirResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSDeleteRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="DeleteDir" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSDeleteResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSDownloadRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSDownloadResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="FileData" type="xoa:DocDataType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSListRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="IncludeSubDir" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:simpleType name="EntryType">
<xs:restriction base="xs:string">
<xs:enumeration value="file"/>
<xs:enumeration value="directory"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="CFSListResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="DirectoryEntry" type="xoa:DirectoryEntryType">
<xs:annotation>
<xs:documentation>content of
DirectoryEntry is path relative to
the RelativePath</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DirectoryEntryType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" type="xoa:EntryType" use="required"/>
<xs:attribute name="modified" type="xs:dateTime" use="optional"/>
<xs:attribute name="size" type="xs:integer" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSRenameRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="OldRelativePath" type="xs:string"/>
<xs:element name="NewRelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSRenameResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="OldRelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="NewRelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSUploadRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element name="FileData" type="xoa:DocDataType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSUploadResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- ===============================
<xs:include schemaLocation="AddressType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
<xs:include schemaLocation="EncodableStringType.xsd"/>
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
=============================== -->
<!-- Type definitions -->
<!-- Phone element -->
<xs:element name="Phone">
<xs:simpleType>
<xs:restriction base="xs:string">
<!-- <xs:pattern value="[0-9+x\-() ]{5,20}"/> -->
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- Email element -->
<xs:element name="Email">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="2"/>
<!-- <xs:pattern value="[@]{1,64}@([@\.]{1,64}\.){1,10}[^@\.]{1,64}"/> -->
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- Eformat type -->
<xs:simpleType name="EformatType">
<xs:annotation>
<xs:documentation> Only used in messageREACH.
Indicates the preferred email format of the
message body the recipient will receive.
Leaving the field empty or setting it to
"default" will send a multipart message body
rather than just a single message body if
it would do so normally. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="html"/>
<xs:enumeration value="htmllite"/>
<xs:enumeration value="default"/>
</xs:restriction>
</xs:simpleType>
<!-- insert list element -->
<xs:element name="InsertList">
<xs:complexType>
<xs:choice>
<xs:element maxOccurs="unbounded" name="Insert">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="number" type="xs:integer"/>
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
<!-- extension element -->
<xs:complexType name="SegmentType">
<xs:choice>
<xs:element maxOccurs="unbounded" name="Property">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="name" type="xs:string"/>
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:choice>
<xs:attribute name="name" type="xs:string"/>
</xs:complexType>
<xs:element name="Extension">
<xs:complexType>
<xs:choice maxOccurs="unbounded">
<xs:element name="Segment" type="xoa:SegmentType"/>
</xs:choice>
</xs:complexType>
</xs:element>
<!-- field mapping type -->
<xs:complexType name="FieldMappingType">
<xs:annotation>
<xs:documentation> Describes the correspondence
between the segment/keyword pairs in the
XDDS header file and columns in a table. Only
two table formats currently supported: CSV
(comma-separated values) and XSL (Excel
spreadsheet). The mapping may go either
from field name to the segment/keyword pair
or vice versa. In both cases, the same
structure may be used. </xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="Map">
<xs:complexType>
<xs:sequence>
<xs:element name="FieldName" type="xs:string"/>
<xs:element minOccurs="0" name="SegmentName" type="xs:string"/>
<xs:element name="PropertyName" type="xs:string"/>
<xs:element minOccurs="0" name="IsBase64Encoded" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<!-- class definitions -->
<!-- delivery item base class -->
<xs:element abstract="true" name="DeliveryItem" type="xoa:DeliveryItemType"/>
<xs:complexType abstract="true" name="DeliveryItemType">
<xs:attribute name="ref" type="xs:string" use="optional"/>
<xs:attribute name="refb64" type="xs:string" use="optional"/>
</xs:complexType>
<!-- new branch -->
<!-- delivery item container class -->
<xs:element abstract="true" name="DeliveryItemContainer" type="xoa:DeliveryItemContainerType"/>
<xs:complexType abstract="true" name="DeliveryItemContainerType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemType"/>
</xs:complexContent>
</xs:complexType>
<!-- list delivery item class -->
<xs:element name="List" type="xoa:ListType"/>
<xs:complexType name="ListType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element name="Name" type="xs:string"/>
</xs:sequence>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- SmQuery delivery item class -->
<xs:element name="SmQuery" type="xoa:SmQueryType"/>
<xs:complexType name="SmQueryType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element name="Name" type="xs:string"/>
</xs:sequence>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- External table delivery item class -->
<!-- This includes CSV and XLS files -->
<xs:element name="Table" type="xoa:TableType"/>
<xs:complexType name="TableType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element minOccurs="0" name="FieldMapping" type="xoa:FieldMappingType"/>
<xs:choice>
<xs:element name="DocRef" type="xs:string"/>
<xs:element name="Document" type="xoa:DocumentType"/>
</xs:choice>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- new branch -->
<!-- delivery item simple class -->
<xs:element abstract="true" name="DeliveryItemSimple" type="xoa:DeliveryItemSimpleType"/>
<xs:complexType abstract="true" name="DeliveryItemSimpleType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemType">
<xs:sequence>
<xs:element minOccurs="0" name="Alternate">
<xs:complexType>
<xs:choice>
<xs:element ref="xoa:Fax"/>
<xs:element ref="xoa:Internet"/>
<xs:element ref="xoa:Voice"/>
<xs:element ref="xoa:Fod"/>
<xs:element ref="xoa:Mbox"/>
<xs:element ref="xoa:Sms"/>
<xs:element ref="xoa:Telex"/>
<xs:element ref="xoa:DeliveryItemGeneric"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- mbox delivery item class -->
<xs:element name="Mbox" type="xoa:MboxType"/>
<xs:complexType name="MboxType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="UserId" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- telex delivery item class -->
<xs:element name="Telex" type="xoa:TelexType"/>
<xs:complexType name="TelexType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="Number" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- FOD delivery item class -->
<xs:element name="Fod" type="xoa:FodType"/>
<xs:complexType name="FodType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="Address" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- SMS delivery item class -->
<xs:element name="Sms" type="xoa:SmsType"/>
<xs:complexType name="SmsType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- new branch -->
<!-- Complex delivery item class -->
<xs:element abstract="true" name="DeliveryItemComplex" type="xoa:DeliveryItemComplexType"/>
<xs:complexType abstract="true" name="DeliveryItemComplexType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element minOccurs="0" ref="xoa:InsertList"/>
<xs:element minOccurs="0" ref="xoa:Extension"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- fax delivery item class -->
<xs:element name="Fax" type="xoa:FaxType"/>
<xs:complexType name="FaxType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
<xs:element minOccurs="0" name="Att" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="To" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="Salutation" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- voice delivery item class -->
<xs:element name="Voice" type="xoa:VoiceType"/>
<xs:complexType name="VoiceType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- internet delivery item class -->
<xs:element name="Internet" type="xoa:InternetType"/>
<xs:complexType name="InternetType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Email"/>
<xs:element minOccurs="0" name="Subject" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="Eformat" type="xoa:EformatType"/>
<xs:element minOccurs="0" name="Password" type="xs:string">
<xs:annotation>
<xs:documentation> Only used in
messageREACH. The password used
by this recipient to retrieve
pull attachments. </xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- fax delivery item class -->
<xs:element name="DeliveryItemGeneric" type="xoa:DeliveryItemGenericType"/>
<xs:complexType name="DeliveryItemGenericType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element name="Address" type="xs:string"/>
</xs:sequence>
<xs:attribute name="type" type="xoa:AddressType" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- Finally, delivery item list -->
<!-- delivery item list type -->
<xs:complexType name="DeliveryItemListType">
<xs:choice maxOccurs="unbounded">
<xs:element ref="xoa:List"/>
<xs:element ref="xoa:SmQuery"/>
<xs:element ref="xoa:Table"/>
<xs:element ref="xoa:DeliveryItemGeneric"/>
<xs:element ref="xoa:Fax"/>
<xs:element ref="xoa:Internet"/>
<xs:element ref="xoa:Voice"/>
<xs:element ref="xoa:Fod"/>
<xs:element ref="xoa:Mbox"/>
<xs:element ref="xoa:Sms"/>
<xs:element ref="xoa:Telex"/>
</xs:choice>
</xs:complexType>
<!--remove includes later
<xs:include schemaLocation="AddressType.xsd"/>
================ -->
<xs:complexType name="DestinationType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" type="xoa:AddressType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- ===============================
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
=============================== -->
<!-- Elementary definitions go first -->
<xs:element name="CharacterSet" type="xs:string">
<xs:annotation>
<xs:documentation>use ISO names</xs:documentation>
</xs:annotation>
</xs:element>
<!-- Document type -->
<xs:simpleType name="DocFormatType">
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="XMF"/>
<xs:enumeration value="TIFF"/>
<xs:enumeration value="XAR"/>
<xs:enumeration value="PS"/>
<xs:enumeration value="PCL"/>
<xs:enumeration value="PDF"/>
<xs:enumeration value="MSW"/>
<xs:enumeration value="WAV"/>
<xs:enumeration value="RTF"/>
<xs:enumeration value="XLS"/>
<xs:enumeration value="HTML"/>
<xs:enumeration value="HTMLLITE"/>
<xs:enumeration value="unspec"/>
<xs:enumeration value="GIF"/>
<xs:enumeration value="JPEG"/>
<xs:enumeration value="PPT"/>
<xs:enumeration value="BMP"/>
<xs:enumeration value="VSD"/>
<xs:enumeration value="PUB"/>
<xs:enumeration value="MPP"/>
<xs:enumeration value="empty"/>
<!-- We do not need to know the document type for the -->
<!-- email attachments. -->
</xs:restriction>
</xs:simpleType>
<!-- Document Encoding format -->
<xs:simpleType name="DocEncodingFormat">
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="base64"/>
</xs:restriction>
</xs:simpleType>
<!-- Document embedded into the request -->
<xs:complexType name="DocDataType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="format" type="xoa:DocEncodingFormat" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- All supported stored object types -->
<xs:simpleType name="SosObjectType">
<xs:restriction base="xs:string">
<xs:enumeration value="tts"/>
<xs:enumeration value="vcs"/>
</xs:restriction>
</xs:simpleType>
<!-- The types of the sos stored objects -->
<xs:complexType name="SosObjectIdType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="sosType" type="xoa:SosObjectType" use="required"/>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- Another Document type -->
<xs:complexType name="DocumentType">
<xs:sequence>
<xs:element name="DocType" type="xoa:DocFormatType"/>
<xs:element minOccurs="0" name="Filename" type="xs:string"/>
<xs:choice>
<xs:element name="DocData" type="xoa:DocDataType"/>
<xs:element name="DocCfs" type="xs:string"/>
<xs:element name="DocUrl" type="xs:anyURI"/>
<xs:element name="SosObject" type="xoa:SosObjectIdType"/>
</xs:choice>
<xs:element minOccurs="0" ref="xoa:CharacterSet"/>
</xs:sequence>
<xs:attribute name="ref" type="xs:string" use="optional"/>
</xs:complexType>
<!-- The document set type -->
<xs:complexType name="DocumentSetType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="Document" type="xoa:DocumentType"/>
</xs:sequence>
</xs:complexType>
<!-- The document by value or by reference -->
<xs:complexType name="DocumentOrRefType">
<xs:choice>
<xs:element name="DocRef" type="xs:string">
<xs:annotation>
<xs:documentation>must refer to a document
in document_set</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Document" type="xoa:DocumentType"/>
</xs:choice>
</xs:complexType>
<xs:complexType name="EncodableStringType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!--includes for standalone validation
================ -->
<xs:simpleType name="HistoryActionType">
<xs:restriction base="xs:string">
<xs:enumeration value="inserted"/>
<xs:enumeration value="updated"/>
<xs:enumeration value="deleted"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="ItemCountType">
<xs:simpleContent>
<xs:extension base="xs:integer">
<xs:attribute name="type" type="xoa:HistoryActionType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="HistoryType">
<xs:sequence>
<xs:element name="Action" type="xs:string"/>
<xs:element name="Operator" type="xs:string"/>
<xs:element name="Agent" type="xs:string"/>
<xs:element name="Time" type="xs:dateTime"/>
<xs:element name="ItemCount" type="xoa:ItemCountType"/>
</xs:sequence>
</xs:complexType>
<!-- ================
<xs:include schemaLocation="AddressType.xsd"/>
<xs:include schemaLocation="DestinationType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
<xs:include schemaLocation="JobIdType.xsd"/>
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="RecStatusType.xsd"/>
================ -->
<xs:simpleType name="JobCancelType">
<xs:annotation>
<xs:documentation>The set of cancellation types/options</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="All"/>
<xs:enumeration value="Deliveries"/>
<xs:enumeration value="Reports"/>
<xs:enumeration value="AcceptanceReport"/>
<xs:enumeration value="CancellationNotice"/>
<xs:enumeration value="Pulls"/>
<xs:enumeration value="FriendDeliveries"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="JobCancelItemType">
<xs:sequence>
<xs:element name="JobId" type="xoa:JobIdType">
<xs:annotation>
<xs:documentation>requested JobId</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="CancelType" type="xoa:JobCancelType"/>
<xs:element minOccurs="0" name="NotificationAddress" type="xoa:DestinationType"/>
<xs:choice minOccurs="0">
<xs:element name="NotificationType" type="xs:string"/>
<xs:element name="NotificationText" type="xoa:DocDataType"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
&Hi,
Not all data types from WSDL are supported during import. There is SAP Note about it.
please read it:
/people/kevin.liu/blog/2005/10/07/a-note-on-wsdl-and-xsd-imports--part-ii
regards,
wojtek
Message was edited by: Wojciech Gasiorowski -
Service interface not listed in business system in ID.
Hi Experts,
In my QA system service interfaces are not listed in business system in ID, i have added product and SWCV in SLD and i am still unable to see the service interfaces of SWCV that i have added. i have done SLD and CPA cache refresh, restarted the QA system but still unable to resolve the issue.
Please suggest how to resolve this issue.Hi Venu,
i have done SLD and CPA cache refresh, restarted the QA system but still unable to resolve the issue.
Try if "Compare from SLD" works? This can be accessed by going to ID -> double-click business system -> communication component -> adapter specific identifiers
Regards,
Mark -
To Monitor inbound and outbound messages for ECC 6.0 business system
Hi Guys,
I am working on ABAP proxy. I want to monitor the flow of Inbound and Outbound messages for my Business system (ECC 6.0).
XI server is on a different system.
I understand that SXMB_MONI is used for tracking XML messages. What kind of tracking can we do by this transaction in our Business system and the XI system?
And how do I know whether the outbound XML message sent is lying in the Sending Business system or in the XI system?
When I am testing my interface, there is a fault message generated. How do I know whether the fault message is being sent to XI?
Thanks,
James.James,
Go to SXMB_MONI in your sending system.
Here you will find a message ID fro your Message.
Go to XI, --> SXMB_MONI -->Monitor For Processed XML messages --> Advanced Selection Crieteria and use the Message ID here to see if the Message has hit XI or not.
Likeiwse it can be traced in the target system as well.
The basic point, The messages will have same Message Id on your R3 and on XI.
Regards
Bhavesh -
No interfaces listed for ECC Business System in PI 7.1 for intrf. Detrm
Hi all,
I have come across this situation earlier, did some settings in SLD ..tech system...(Don rembr it nw....)
I am not able to see the list of interfaces for an ECC Bus.System during Interface determination,
I manually have to key in the name of the BAPI instead of the values appearing in the value list....
I am sure that the is something missing while havin created the BS and TS in the SLD,
Can someone guide me what my approach would be.
Replies much appreciated. ThanksHi
Please assign the software component(Product) in which you have imported your BAPI in IR to your
Business System in SLD.
Then you can see all the interfaces of that software component in your Business System(ECC) in ID.
So just add the software component to your Business System in SLD then you can get the interface in
ID.
Check the following link for the same issue.
Re: No interface Idoc in Business system Receiver
Thanks
Prasad Nemalikanti -
Unable to see interface on ASA 5510 Firewall
Hi All,
I am unable to see 4th interface on my firewall i.e fastether0/3 on my firewall ASA 5510.
Below is the output.
ciscoasa# sh int ip br
Interface IP-Address OK? Method Status Protocol
Ethernet0/0 x.x.x.x YES CONFIG up up
Ethernet0/1 x.x.x.x YES CONFIG up up
Ethernet0/2 unassigned YES unset administratively down down
Internal-Control0/0 127.0.1.1 YES unset up up
Internal-Data0/0 unassigned YES unset up up
Management0/0 192.168.1.1 YES CONFIG up up
Please suggest what could be the reason.
Regards
PankajHi Ramraj,
Even i have the base license for my ASA 5510 which is showing all the 4 interfaces in sh ver. I don't think so license would be an issue. There should be some IOS code bug that needs to be upgraded. If this goes for an OS upgrade it should get resolved.
Its not showing up in sh ver . As Karsten said he might be running on old IOS version.
fy-a# sh ver
Cisco Adaptive Security Appliance Software Version 8.4(4)1
Device Manager Version 6.4(5)
Compiled on Thu 14-Jun-12 11:20 by builders
System image file is "disk0:/asa844-1-k8.bin"
Config file at boot was "startup-config"
fy-a up 1 day 1 hour
Hardware: ASA5510, 1024 MB RAM, CPU Pentium 4 Celeron 1600 MHz
Internal ATA Compact Flash, 256MB
BIOS Flash M50FW016 @ 0xfff00000, 2048KB
Encryption hardware device : Cisco ASA-55x0 on-board accelerator (revision 0x0)
Boot microcode : CN1000-MC-BOOT-2.00
SSL/IKE microcode: CNLite-MC-SSLm-PLUS-2.03
IPSec microcode : CNlite-MC-IPSECm-MAIN-2.06
Number of accelerators: 1
0: Ext: Ethernet0/0 : address is 2c54.2d0c.8f1a, irq 9
1: Ext: Ethernet0/1 : address is 2c54.2d0c.8f1b, irq 9
2: Ext: Ethernet0/2 : address is 2c54.2d0c.8f1c, irq 9
3: Ext: Ethernet0/3 : address is 2c54.2d0c.8f1d, irq 9
4: Ext: Management0/0 : address is 2c54.2d0c.8f1e, irq 11
5: Int: Not used : irq 11
6: Int: Not used : irq 5
Licensed features for this platform:
Maximum Physical Interfaces : Unlimited perpetual
Maximum VLANs : 50 perpetual
Inside Hosts : Unlimited perpetual
Failover : Disabled perpetual
VPN-DES : Enabled perpetual
VPN-3DES-AES : Enabled perpetual
Security Contexts : 0 perpetual
GTP/GPRS : Disabled perpetual
AnyConnect Premium Peers : 2 perpetual
AnyConnect Essentials : Disabled perpetual
Other VPN Peers : 250 perpetual
Total VPN Peers : 250 perpetual
Shared License : Disabled perpetual
AnyConnect for Mobile : Disabled perpetual
AnyConnect for Cisco VPN Phone : Disabled perpetual
Advanced Endpoint Assessment : Disabled perpetual
UC Phone Proxy Sessions : 2 perpetual
Total UC Proxy Sessions : 2 perpetual
Botnet Traffic Filter : Disabled perpetual
Intercompany Media Engine : Disabled perpetual
This platform has a Base license.
Serial Number: JMX1AXXXXX
Running Permanent Activation Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Configuration register is 0x1
Configuration has not been modified since last system restart.
fy-a#
Ramraj please do correct me if am wrong.
Please do rate if the given information helps.
By
Karthik -
Can not see messages in SXMB_MONI of ECC
Hi Friends,
Here I am facing some problem with SXMB_MONI of ECC. I am doing an XI upgrade from XI3.0 to PI 7.1.
when I am doing my interface upgrade I am unable to see messages in SXMB_MONI of ECC. As ECC is also got upgraded now BASIS is very confused about configuration.
when I went through some blogs I came across some suggestions like configuration in SXMB_ADM. In ECC the integration engine configuration what I did is
Role of Business System : Application System.
Corresponding Integ. Server : dest://<HTTP DEST>
One of my doubts:: Is <HTTP DEST> is the one which we are giving in XI/PI or the new one created for ECC. First BASIS set up <HTTP DEST> as the same one which was configured in PI. Then I went back to BASIS and tell them that ECC is having its own local Integration Engine, so we need to create <HTTP DEST> which connects to integration engine of ECC.
Then they created one <HTTP DEST> for ECC. but when I am doing connection test, Http response is coming as 400 BAD HTTP Response :: protocol error. I have no idea why it is behaving like that.
After when I go through some more blogs they are dealing with RFC destinations LCRSAPRFC and SAPSLDAPI. when I check it in ECC I didn't found RFC destination LCRSAPRFC but SAPSLDAPI is existing in ECC.
more over some blogs deal with the configuration in Transaction SLDAPICUST. when I check it in ECC no configuration was done in SLDAPICUST.
I already configured ENGINE_TYPE, IS_URL, LOGGING, LOGGING_PROPAGATION, LOGGING_SYNC under specific configuration data of SXMB_ADM of ECC.
Please let me know what needs to be done and let me out of this confusion. As I am a PI developer I am unaware of all these configurations. expecting replies from gurus....
Regards,
DASARIHi Friends,
Looking at some more blogs I got a doubt.
Actually my scenario is File - XI - RFC.
Now my doubt is whether we can see the messages which were going to ECC by RFC adapter ?
Looking at a thread I got confused whether SXMB_MONI can capture messages only if they are coming from Proxy or IDOC . please clarify me.
Regards,
Dasari. -
Wired computers unable to see printer on Airport Express...help?
Hi all,
I recently set up an Airport Extreme on our office network to offer wireless network access piggybacked on our wired router. I then purchased an Airport Express which I was planning on using as a wireless print server for our Canon i9900 for all office computers connecting wired or wirelessly, which would interface with the network via the Airport Extreme Base Station.
I have configured the Express as an extension of the existing Airport network, and attached the printer to it via USB. All the computers in the office which have airport cards onboard can see and print from the printer, which is great. The problem is that all of the computers connecting to the network via wires are unable to see the printer (this is under both 10.3.x and 10.4.x, all airport software completely updated.) The Extreme base station shows up for all office computers in their Airport Admin Utility, AND if the printer is connected directly to the Extreme Base Station via USB, all computers can see the printer over Bonjour/Rendevous.
Anybody have ideas as to how I can get my wired machines to see the printer on the Airport Express?
Thanks!!Applications > Utilities > Airport Admin Utility
Scan and Select your Airport
Click Configure
On the Airport Tab
Base Station Options...
Check Enable Remote Printer Access
iFelix -
Sync to Asyn Message interface mapping
Hi all,
I have a scenario where source message interface is a sync interface and target is async. Can any body suggest if it is possible to map the request message structure of source to target (async) and the response need to have a fixed value.
Is it required to use BPM or is it possible without BPM. Can any body please suggest? Any help will be appreciated.
Thanks
-KulwantHi,
Defining Sync/Async Communication
Use
To enable the communication between a synchronously calling business system (synchronous outbound interface) and an asynchronously called business system (asynchronous inbound and outbound interface), you can define a sync/async bridge in an integration process. You can only define one sync/async bridge for each integration process.
You can also achieve sync/async communication by using the JMS adapter. If you do not have any particular demand for monitoring or for troubleshooting, SAP recommends that you use sync/async communication in the JMS adapter instead. The advantage of using the JMS adapter over synch/async communication using an integration process is a significant increase in system performance.
See: Async/Sync and Sync/Async Bridge in JMS Adapter
We use Sync/Async bridge to establish the Sync communication between the Applications.
Normally the Technical adapters like File will not support the Sync communication to send back the Response to the Sender system from the File system.
So in this case we will use Sync/Async bridge to establish the connection using BPM.
Check these
Bridging the Sync-Async bridge with Fork (XI)
Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi
Structure of a Sync/Async Bridge
The following table outlines the minimum components of a sync/async bridge:
*Step
Use*
Receive step to open the sync/async bridge
Receives the message request from the synchronously calling business system and opens the sync/async bridge
Asynchronous send step
Sends the received message asynchronously to the asynchronously called business system
Receive step
Receives the message from the asynchronously called business system
Send step to close the sync/async bridge
Sends, for example, the response from the asynchronously called business system to the synchronously calling business system
Performance Considerations
If you insert additional steps in the sync/async bridge, the synchronous time is increased correspondingly. If the time that elapses before the sync/async bridge is closed is too long, this can lead to problems.
Fault Messages
It is currently not possible to send fault messages back to the synchronously calling business system. If you want to return error statuses to the synchronously calling business system, you can define a field for an error indicator in the message that is sent to the synchronous interface.
Procedure
Define a Receive Step to Open the Sync/Async Bridge
1. Insert the receive step to open the sync/async bridge in the integration process.
*You can do this at the following points: *
Directly after the start marker
As the first step in a block if the block is the first step of the integration process and if it has the mode Standard
As the first step in a fork. If the fork already contains some starting receive steps, the Start Process indicator is automatically reset for these steps.
2. In the object area, define the container element that receives the synchronously sent message.
Specify an asynchronous, abstract interface in the container element. The message must correspond to the request message of the synchronous interface used to receive the message.
3. Select this container element in the Message field in the properties area of the receive step.
4. In the Mode field, select Open S/A Bridge.
5. Select the Start Process field.
The receive step to open the sync/async bridge must start the integration process. There must be no other receive steps to start the integration process.
6. Specify the synchronous interface for receiving the message from the synchronously calling business system. The message type of the message to be received and the request message from the synchronous interface must be identical.
Define an Asynchronous Send Step
7. Insert a send step that sends the received message asynchronously to the asynchronously called business system.
See also: Sending Messages from Integration Processes Asynchronously
Define a Receive Step
8. Insert a receive step that receives the message from the asynchronously called business system.
Define a Send Step to Close the Sync/Async Bridge
9. Insert the send step at the required position in the process definition.
Do not insert the send step in a loop, block, or fork.
10. In the Mode field, select Close S/A Bridge.
The integration process must not contain any further send steps to close a sync/async bridge.
11. In the Opened By field, specify the receive step that opened the sync/async bridge.
12. In the message field, specify the message that is sent to the synchronous interface.
This message must be of the same type as the response message from the synchronous interface that you specified in the opening receive step.
Example
You can find an example of a sync/async bridge in the Integration Repository under SAP Basis à SAP Basis 6.40, namespace http://sap.com/xi/XI/System/Patterns under BpmPatternSyncAsyncBridge.
For a description of the example, see Example: Sync/Async Communication.
BPM is an additional advantage of Netweaver XI. it provides features like Sync-Async Bridge, Async-Sync Bridge, stateful msgt processing.....so on.
Sync-Async Bridge acts as a bridge between a synchronous Business system and Asynchronous business system.
forex: if u r communicating with a synchronous RFC to a File system(always asynchronous, which is not able to send any response to synchronous RFC Interface).
In this kind of scenarios BPM Sync-Async Bridge enables communication between a Synchronous RFC to Asynchronous File system or vice versa..
Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages
Plz go thru the following:
- Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] - Use of Synch - Asynch bridge in ccBPM
Asyn - Synch BPM -
http://help.sap.com/saphelp_nw70/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/43/65d4dab39b0398e10000000a1553f6/content.htm
Example on Sync/Async communication:
http://help.sap.com/saphelp_nw04s/helpdata/en/43/65d4dab39b0398e10000000a1553f6/frameset.htm
Thanks,
Swathi -
Message Interface to Business System
Hi
Here is my SCenario
Can anyone let me know how can I add a Inbound Interface to the existing Business System, on the receiver Tab,
I have message interface in ESR and needs to add to the business component, Do not see any option to add new message
Your input is hilgly appreciated
Thanks
PRHi...
If I am not wrong, then you are developing your interface in PI7.1. Correct me if my assumption is wrong.
You have to add your software components to the business system in the SLD, then only the MI will pop up in the inbound list.
Till PI 7.0, you could select the "ALL" and any inbound to the BS, but the correct way is to add the S/w component to your business system and then use the message interface in your interface determination/receiver determination.
Thanks,
Pooja Pandey -
Message interface not exist in any software components on business system
Hi Experts,
In development-environment we have an interface (SAP->XI->3rd party system) with a conditional receiver determination (based upon a fieldvalue in RFC that comes from SAP, "CONTROL_RECEIPE_DOWNLOAD"). This functions properly in development.
After transport to production environment this structure is not known when I try to use it in the Integration Directory when creating a conditional receiver determination. Double-click on the interface does result in the startup of the integration builder, but the interface itself can not be found. The following error-message appears:
"Error message Message interface does not exist in any software components installed on this business system"
All design-objects have been put into production and in Integration Builder the structure is available. In IR it is not...
In development In the business system of the sending SAP system, I can see the interface. In production, I don't see any interfaces at the business system....so this might be the problem but how can I add an interface manually to a business system?
Can anybody please help?
Thanks in advance
WilliamHi William,
One more thing. In Production, check the technical system of source. SWCV in which you have developed your interface, should be installed on the source system. If this SWCV is not in list of your installed products & SWCV then add it. Update the business sytem in ID again & it will work. I guess you have done a typo by saying that objects are not available in IR but in Integration builder its avaliable.
Regards
Sushil
Maybe you are looking for
-
Ipod mini and nan2nd not recognised by windows or itunes
Had ipod mini for two years no problems. My son got a nano 2nd gen in november no problems. latest itunes downloaded and none of the above are recognised. tryed all the quick fixes on the help pages and a few on the discussion page nothing works plea
-
Safe sleep or hibernation won't work on my Macbook 13" Unibody (late 2008)
I have a 13" unibody Macbook which I bought in October 2008. The systems sleeps well once the lid is closed but if it runs out of battery it will not hibernate. I checked the output of pmset and everything is properly set for mode 3, which is the "sa
-
Hi all, I have 3 questions 1) What happens if a customer master is created using T-code VD01 and not XD01. 2) Is there any impact this will have. 3) Is it always compulsary to create customer master with XD01. Thanks Vikrant
-
1434891 - Consolidation fails in BOFC 7.5 (new installation)
Hello, maybe someone can help me. There's a error in the consolidation of my Business Objects Financial Consolidation application: Failed to run database query:".. The SAP recommended solution (1434891 - Consolidation fails in BOFC 7.5 (new installat
-
Unable to update itunes 7.7 - 32 bit issue....please help
I tried to update my itunes on my laptop and keep getting the following error message: The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need an x86 (32-