Umlaut Conversion issue in Sender communication channel SAP PI
Hi Gurus,
We are facing issue while conversion.
umlaut Conversion issue in Sender communication channel that is reason channel not able to pic the file from the path.
Sender CC error:
Value of incoming field is too large. Segment:'IMD', Field:'7008', MaxLength:'35', value:'Plssvvkbecher Lübzer 0,4 (1280Stk p' DESCRIPTION: The length of the field value is too big !
Actually field contains 35 Chars only the value is : 'Plssvvkbecher Lübzer 0,4 (1280Stk p'
We tried with “ISO-8859-1” if the field value is less than 35 characters it is able to converting.
Please help me out from this issue.
Thank you.
Regards,
Jittu.
Hi Jittu,
Have you tried using the codepageconversion bean in the modules under the sender? It would be like:
AF_Modules/TextCodepageConversionBean with a parameter of Conversion.charset and a value of utf-8.
Regards,
Ryan Crosby
Similar Messages
-
Content conversion at JMS sender communication channel
Hi friends,
I have to convert fixed length flat structure to xml message.Therefor i have to do content conversion at the JMS sender comm channel.Can someone please explainthe procedure?
data in the queue would be like as follows.
9999000000124646q12233appej500rc11147822zordHi Manikandan,
The structure conversion can handle files containing rows with different structures. In
each row there is a key field to identify the structure. The rows with identical key fields of
course have identical structures.
Let us assume that we have a sample file with four rows. Each row has a two-byte key
field; the first row has a second field with ten bytes; the structure of the second and third
rows is the same and comprises two additional fields with three bytes each; the last row
has a second field with five bytes:
AA1234567890
BBABCABC
BBXYZXYZ
CC12345
The configuration for the conversion could look like this:
Module Configuration
Module Key Parameter Name Parameter Value
Plain2XML Transform.Class com.sap.aii.messaging.adapter.Conversion
Plain2XML Transform.ContentType text/xml;charset=utf-8
Plain2XML xml.conversionType StructPlain2XML
Plain2XML xml.processFieldNames fromConfiguration
Plain2XML xml.documentName MyDocument
Plain2XML xml.documentNamespace http://xi.com/test
Plain2XML xml.recordsetName MyRecordset
Plain2XML xml.recordsetStructure NameA,1,NameB,*,NameC,1
Plain2XML xml.keyFieldName MyKey
Plain2XML xml.keyFieldType CaseSensitiveString
Plain2XML xml.NameA.fieldNames MyKey,field-nameA
Plain2XML xml.NameA.fieldFixedLengths 2,10
Plain2XML xml.NameA.keyFieldValue AA
Plain2XML xml.NameB.fieldNames MyKey,field-nameB1,field-nameB2
Plain2XML xml.NameB.fieldFixedLengths 2,3,3
Plain2XML xml.NameB.keyFieldValue BB
Plain2XML xml.NameC.fieldNames MyKey,field-nameC
Plain2XML xml.NameC.fieldFixedLengths 2,5
Plain2XML xml.NameC.keyFieldValue CC
In xml.recordsetStructure, you add a name for each different structure followed by the
number of occurrences or an asterisk for unbounded occurrences. For each structure
name, you configure the structure separately in a separate namespace such as
xml.NameA.fieldNames and so on.
If your source file is a CSV file, replace each xml.XXX.fieldFixedLengths with
xml.XXX.fieldSeparator.
the result of this conversion looks like this:
<ns:MyDocument xmlns:ns="http://xi.com/test">
<MyRecordset>
<NameA>
<MyKey>AA</MyKey>
<field-nameA>1234567890</field-nameA>
</NameA>
<NameB>
<MyKey>BB</MyKey>
<field-nameB1>ABC</field-nameB1>
<field-nameB2>ABC</field-nameB2>
</NameB>
<NameB>
<MyKey>BB</MyKey>
<field-nameB1>XYZ</field-nameB1>
<field-nameB2>XYZ</field-nameB2>
</NameB>
<NameC>
<MyKey>CC</MyKey>
<field-nameC>12345</field-nameC>
</NameC>
</MyRecordset>
</ns:MyDocument>
Regards,
Vinod. -
JMS sender communication channel content conversion
Hi,
I struck with the content conversion in the JMS Sender communication channel.
I have configured the communication channel with the filed fixed lengths. (Simple type)
The field fixed lengths i have given are 10,2,3,11
The contents in the file 1000000072 230 111
but, in the input xml after conversion iam getting 100000007 in the first field and 2 in the second field 23 in the third field.
I have configured the sender communication channel as in the document in SDN.
Even, i configured several communication channels. I didn't get this strange error any time.
I have gone through SDN to fix this issue, but i didn't get solution.
If anyone got rectified this kind of error, please answer your solution to me
Thanking you,
Regards,
Krishnaraju.Hi,
Thanks for all your support. The issue got resolved.
The issue is due to the file, In the file the special characters are appearing. We are not able to see these characters in the notepad, wordpad, text editor.
But, these characters are appearing in th syn text editor. So, we removed those characters and processessed the file. Now, it is successfull.
Regards,
Krishnaraju. -
BIC Module Error in Sender Communication channel for EDI to File scenario.
Hi Experts,
We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
Thanks & Regards,
AbhishekHi Abhishek,
Is there any special character present in the EDI file?
the parser is not able to parse the data.
you can check the BIC conversion log for more information.
Regards,
Harish -
JMS Sender Communication Channel problem
Hi XI gurus!!
I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
In defaultTrace.XX.trc I see the following information and errors:
#1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
#1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
{GenericConnectionProfileImpl
{Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
JmsMessageSelector=,
ConnectionFactoryConstructor=null,
ConnectionFactoryFactoryInvocation=null,
ConnectionFactoryInvocations=[],
DestinationConstructor=
{ConstructorInvocation
{className=null,
invokeParams=[]
DestinationInvocations=[],
MessageInvocations=[],
DestinationName=null,
User=,
Password=,
isJmsSessionTransacted=true,
InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
LookupConnectionFactory=QueueConnectionFactory,
LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
SerializedConnectionFactoryPath=null,
SerializedDestinationPath=null,
Flags=0000000000000000000000000000000000000000000000000000100000000010
#1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
#1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
#1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
ThanksHI,
As per the trace details given please consider few of the below options....
What do u see in adapter monitoring tool for JMS adapter?
http://hostname:5XX00/mdt/amtServlet
Did you follow the document on correlation of JMS messages?
In communication channel You have to set
Correlation ID -> XI conversationID
XI message ID->GUID
XI Conversation ID -> JMS correlation ID.
Now in the custom J2EE application you should set
jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
This thread deals with the issue..
JMS Queue monitoring
Check if the JMS Sender adapter EOIO is with serialized messages
Thanks
Swarup -
File Structure - Sender Communication Channel
Hi All,
My Sender flat file structure is below like this
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
I did the Sender Communication Channel configuration - Content Conversion
Document Name : XXX
Document NameSpace: XXXX
Recordset Structure: MT_Test,*
Recordset Sequence: Ascending
Key field Type: String Case-Sensitvie
MT_Test.fieldNames: Filed1,Field2,Field3,Field4,Field5,Field6
MT_Test.fieldSeparator: '|'
MT_Test.additionalLastFileds: ignore
MT_Test.endSeparator : 'nl'
ignoreRecordsetName: true.
But its pick the file, In SXMB_Moni show Currect...
But in Runtime workbench, in Communication Channel moni, it show below like this,
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_Test xmlns:ns0="http://XXXXX">
<JOBS />
</ns0:MT_Test>
What is the Issue, where i missed some thing, In message mapping, its correct..
Thanks.
SRSR,
I am still little confused with your below statement.
But its pick the file, In SXMB_Moni show Currect...
But in Runtime workbench, in Communication Channel moni, it show below like this,
>
> <?xml version="1.0" encoding="UTF-8" ?>
> - <ns0:MT_Test xmlns:ns0="http://XXXXX">
> <JOBS />
> </ns0:MT_Test>
You mean to say that in MONI, the mapping output is fine, but when you check the output at RWB -> CC Monitoring for the Sender Channel, then you get the above mentioned XML?
This means that there is nothing wrong with your source CC settings. If the entry in RWB -> Sender CC is wrong, your MONI entry will never be right. So, this is really weird.
What is the source structure that you have defined in DT?
Regards,
Neetesh
Edited by: Neetesh Raj on Sep 29, 2009 2:31 PM -
Sender Communication Channel Error
Hi all,
iam working on JDBC scenario.For this iam using party and business service.
iam getting following error at jdbc sender communication channel.
Error occurred while sending message: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.
Erlier it worked fine.But now iam getting this problem.
We are having some other channels which r working fine.
any ideas......?
Thanks,
Sreedhar Goud.1. If you know the user, who having admin rights;
1.Open the VA tool; ex: C:\usr\sap\X67\JC01\j2ee\admin --> click on "go.bat"
2. Click on "New" button ( this is on Logon Dialog box)
3. Enter "Display name"; and select "Direct Connection To a Dispatcher Node".
4. Say "Next"
5. Enter "User Name","Host" and "Port" and Save the data.
6. Select User and click on "Connect"
2. Did you forget the J2EE_ADMIN password? Just follow below steps:
Just follow below steps:
1.Start the Config Tool C:\usr\sap\<SID>\<engine-instance>\j2ee\configtool\configtool.bat
Ex: D:\usr\sap\F02\JC00\j2ee\configtool --> configtool.bat
2. "Switch to configuration mode" for that Click on "Pencil" icon;
3. Click on "Pencil" icon means "Swith to Configuration Edit mode" then say "YES"
4. cluster_data --> server --> cfg --> services -->
click on "Propertysheet com.sap.security.core.ume.service
select properties:
ume.superadmin.activated = True
ume.superadmin.password = <enter password >
then say "OK"
Click on "Pencial ICON.
5. Save & restart Java Engine.
Login with "Administrator"
1. http://<host>:<Port>/useradmin/index.jsp
2. Enter userid / Password as "Administrator / <password>
3. it will ask change password just change it.
Please follow steps one by one. it should resolve your issue. -
Sharing JMS sender communication channels
Hi all,
We have flatfile interfaces to XI JMS where we would like to share the JMS sender communication channel.
This is normally not possible since you cannot have two sender agreements with the same comm channel.
Are there workarounds for sharing JMS comm channels (we cannot make use of content fields, we do no conversion). is there a way with variables perhaps?
Thanks for any help
TomTom
There is an otption of send a file to multiple receivers.
Therefore use your receiver determination to have multiple receivers and set there some condition.Thus making conditional receivers. Or have two receiver determinations.
This might help you.
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
/people/prasadbabu.nemalikanti3/blog/2006/03/10/bpmsingle-sender-and-multiple-receivers-based-on-synchronous-exchangeswitch-part-1
/people/prasadbabu.nemalikanti3/blog/2006/02/27/collecting-and-bundling-vendor-records-from-different-multiple-interfaces-file-systempeoplesoft-and-sending-to-sap-r3-system-part-2
http://help.sap.com/saphelp_nw04/helpdata/en/7d/577941761b070de10000000a1550b0/content.htm
Pls : Reward points if helpful.
Vishal K -
Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?
Hello All,
One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
Is the (IDoc) Communication Channel from Sending system to XI required to configured?
Many thanks in advanced!
JochenHi Jochen,
for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
Thanks,
Rajeev Gupta -
Error in sender communication channel
Hi,
I am doing File to RFC scenario in which i am using Standard bapi to get the cost from the sap system
while sending the data in sender communication channel the processing mode is in delete mode but it is not deleting and throwing the error
Error: com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException
this error is from sender communciation channel..
can any one give some inputs for this...
regards,
KishoreK.P.N.,
i have checked it getting the same error. in moni also administrative cache clear error is coming
do we need to do any workaround...
regards
Kishore -
JMS (Sender Communication Channel) and MQ in Mainframe (Legacy) System
Hi All,
Can we use JMS Sender Communication Channel in XI that runs on Windows 2003 server to DIRECTLY poll messages from MQ in Mainframe (Legacy) system??
I understand that we can install MQ on XI server and have mainframe push the messages to XI MQ so that JMS can poll but wanted to see if there is a way to do this without having MQ on XI server.
If you know of any documentation regarding this, can you please post it?
Thanks,
JayJung,
Are you looking for this help:
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
Also check this sap help:
http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
---Satish -
JDBC Sender Communication Channel Problem
Hello everybody,
I have a sender communication channel, it is with green Functioning status in channel monitor in runtime workbench, and the log says "Process started" for every pool as configured, but it doesn't return any data to XI, and there's data to be taken, the problem started a few hours cause it was working fine, I've already executed a Complete refresh cache in SXI_CACHE, and changed the channel from Active to Inactive in ID, and Stopped and Started it again in RW, it doesn't give any errors, but it doesn't bring back any data that should be, any suggestions or maybe any information on how to refresh totally those channels????, thanks in advance.
Regard's
PaulHi Paul
Check for JDBC adapter locks. cpa cache locks are not relevant to your problem.
Moreover check with the visual admin logs as well. if you can get info about the issue you have
Thanks
Gaurav -
Inactive Sender Communication Channel still processing Files?
We de-activated the Sender Communication Channel of an interface. However, the file adapter keeps processing?
Anybody know what is going on?
Thank-You.Hi Tom,
1) Check out Whether you have De-activated the Right Adapter.
2) Refresh the Cache,
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
c)Call transaction SM58 to check the status of the refresh process.If no entry for function module SAI_CACHE3_REFRESH_BACKROUND is Present any more the cache update is finished.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss -
PI sender communication channel not reading files from NFS directory
Hello,
I have a sender communication channel configured to read file from NFS directory which is on ECC server. A program in ECC generates the file and puts it on the ECC server in the output directory. PI sender communication channel is supposed to pickup this file and process it. If I give the NFS path as the source directory, I am getting error: Configured source directory '//Server/DIR/OUT' does not exist. I tried putting '
Server\DIR\OUT' too but same error. Do I have to add the NFS path of ECC into PI as logical path?
Any suggestions?
Thanks,
SangitaHello Sangita,
Your ECC server is an external system, therefore you need to activate FTP service in that system and use the transport protocol FTP:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
You can use NFS protocol when you have a local directory in XI server.
Best Regards,
.Luis Bernal. -
Inactivate RNIF sender communication channel
Hi All,
For one of my Prod issues ,we need to inactive RNIF sender communication channels, right now the channel in stop state.
Could any one suggest how to inactivate the RNIF cc.In Integration directory there is no option such to inactivate the channel.
Please provide your inputs
Regards,
VidyaHi Bhogaraju,
You dont have that option for RNIF comm. channel. But as an alternative you can stop the comm. channel in Communication cahnnel monitoring which you already doing. Also you can try to schedule your communication channel according to this blog:
/people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-
Regards,
---Satish
Maybe you are looking for
-
Error in passing parameter between 2 jsp..
Hi.. I have error in when submitting a jsp to another jsp.. It seems like cannot get the values i put in the first jsp... The first jsp codes.. <FORM name="mank" action="<%= HttpPortletRendererUtil.htmlFormActionLink(request, PortletRendererUtil.PAGE
-
Oracle ADF Data Control With Java List
Hello I have a question regarding Data Controls that are based on Application Modules functions. In short I created function: public List getListOfTest() { List allTests = new ArrayList(); allTests.add("test1"); allTests.add("test2"); allTests.add("t
-
Itunes not connected with itunes store via wifi
I have problem in connection between my iphone with itunes store when i am using wifi but its ok when i am using cellular
-
Trigger IDoc DELVRY03 after Inbound Delivery create
Hi, Inbound delivery is created through an Inbound IDoc and I want to trigger an outbound DELVRY03 IDoc when the Inbound Delivery is created. How do I trigger this? Regards, Sneha
-
Error in initiating sqlplus in Linux
sp2-0750: you may need to set oracle_home to your oracle software directory when I check the gedit .bash_profile ORACLE_USER=oacle export ORACLE_USER ORACLE_BASE=/data1/oracle/product/10.2.0 export ORACLE_BASE ORACLE_HOME=/data1/oracle/product/10.2.0