on 02-17-2012 8:25 AM
hi All,
currently i was trying to configure the PI for very simple CASE like how to FTP file XML to XML follow the guide below
but nothing happen after all the configuration for the variant1, the file doesn't created on target folder, anyway how i trace the error? thanks.
Regards
Hariyono
some update my error :
do a test configuration an as result below :
Sender Agreement
<Not found>
<Trace level="1" type="B">SENDER AGREEMENT SIMULATION</Trace>
<Trace level="1" type="T">Simulating Adapter Engine...</Trace>
<Trace level="1" type="T">Simply trying to loolup for the most specific Sender Agreement object</Trace>
<Trace level="1" type="T">no objects found</Trace>
<Trace level="1" type="T">Note that real results may differ</Trace>
Receiver Determination
<Not found>
Runtime error
Message is incomplete. No Sender found
<Trace level="1" type="B">CL_RD_PLSRV-ENTER_PLSRV</Trace>
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="1" type="E">CL_RD_PLSRV-ENTER_PLSRV</Trace>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
any update?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Try the following:
1. Check if the "Create Target Directory" checkbox is marked in your receiver Communication Channel.
2. If yes, and still the directory is not created, then go to Communication Channel Monitoring in Runtime WorkBench for that particular Communication Channel to find the precise error description. For instance, your user might be missing authorization to create directories in tarted location.
Hope this helps,
Greg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Grzegorz Glowacki
1. yes, Create Target Directory checkbox is marked.
2. can't find the Communication Channel Monitoring in "Runtime WorkBench" only got Component Monitoring | Message Monitoring | End-to-End Monitoring | Performance Monitoring | Index Administration | SLD Registration | Configuration | Alert Configuration | Alert Inbox | Cache Monitoring
And i try go to "Message Monitoring" but there is no log at all in there.
Step by step procedure to get to Communication Channel Monitoring:
1. In Component Monitoring of RWB click "Display" button.
2. Click on the "Adapter Engine " in the tree that appears.
3. The "Communication Channel Monitoring" button appears, click it.
4. Provide the Communication Channel name to go to details.
Hope this helps,
Greg
1. channel sender :
2/17/12 5:06:47 PM Polling interval started. Length: 60.0 seconds
2/17/12 5:06:47 PM Processing finished successfully
2/17/12 5:06:47 PM Processing started
2/17/12 5:05:47 PM Polling interval started. Length: 60.0 seconds
2/17/12 5:05:47 PM Processing finished successfully
2/17/12 5:05:47 PM Processing started
2/17/12 5:04:47 PM Polling interval started. Length: 60.0 seconds
2/17/12 5:04:47 PM Processing finished successfully
2/17/12 5:04:47 PM Processing started
2/17/12 5:03:47 PM Polling interval started. Length: 60.0 seconds
2. channel receiver
Server 00 00_22333 Functioning
Communication Channel
XiPatternChannel_FileSender
Processing Details for Cluster Node Server 00 00_22333
2/21/12 10:19:47 AM Polling interval started. Length: 60.0 seconds
2/21/12 10:19:47 AM Processing finished successfully
2/21/12 10:19:47 AM Processing started
2/21/12 10:18:47 AM Polling interval started. Length: 60.0 seconds
2/21/12 10:18:47 AM Processing finished successfully
2/21/12 10:18:47 AM Processing started
2/21/12 10:17:47 AM Polling interval started. Length: 60.0 seconds
2/21/12 10:17:47 AM Processing finished successfully
2/21/12 10:17:47 AM Processing started
2/21/12 10:16:47 AM Polling interval started. Length: 60.0 seconds
XiPatternChannel_FileReceiver
the processing button is green
short log : Functioning
but there is no details for the cluster node server.
anything i miss here?
In ID have you used Integrated configuration
If yes, go to runtime workbench and message monitoring. Input the selection criteria and check if there was any message created. If not then ur sender channel didn't pick up any file
check the source directory/filename if it is correct. Otherwise It could be authorisation or firewall issue
i think the parameter i provided is correct already :
communication channel : XiPatternChannel_FileReceiver
adapter type File
target directory C:\XiPattern2
filename scheme XiPatternSenderFile1.xml
communication channel : XiPatternChannel_FileSender
adapter type File
target directory C:\XiPattern1
filename scheme XiPatternSenderFile1.xml
Hi,
If your sender channel is polling all the time, it means that it found no files to be processed. So no message was processed by PI, and no target file/directory could be created make sure your SENDER communication channel is correct, and that there is any file to be processed in the source directory.
Hope this helps,
Greg
Base on my configuration for communication channel below, it seems like the directory for sender is correct already, anything i miss out? anyway my os is running on windows server 2008 and the firewall already turn off.
communication channel : XiPatternChannel_FileSender
adapter type File
target directory C:\XiPattern1
filename scheme XiPatternSenderFile1.xml
C:\XiPattern1>dir
Volume in drive C has no label.
Volume Serial Number is 6066-D65B
Directory of C:\XiPattern1
02/17/2012 03:30 PM <DIR> .
02/17/2012 03:30 PM <DIR> ..
06/23/2005 05:36 PM 340 XiPatternSenderFile1.xml
06/23/2005 05:41 PM 343 ZXiPatternSenderFile2.xml
2 File(s) 683 bytes
2 Dir(s) 1,485,634,289,664 bytes free
Hariyono Yang wrote:
communication channel : XiPatternChannel_FileReceiver
adapter type File
target directory C:\XiPattern2
filename scheme XiPatternSenderFile1.xml
communication channel : XiPatternChannel_FileSender
adapter type File
target directory C:\XiPattern1
filename scheme XiPatternSenderFile1.xml
if you are using file adapter, with the transport protocol as FTP, then the path name of the ftp location should be generally of unix format, and the directories generally start with /
in somecases, if you are using filesytem(NFS) as transport protocol, its better to use forward slash e.g. C:/directory instead of C:\directory.
regards,
BJagdishwar.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.