Opalis Integration Server: Using Get File Status with a wild card
-
Friday, May 04, 2012 4:51 PM
Hello,
I apologize if I've placed this in the wrong forum, I could not find one that specifically dealt with Opalis Integration Server.
I'm using Opalis Integration Server version 6.2.2.5229 and am trying to use either the Get File Status object to read a file but using a wild card. So my scenario goes like this. I have a process that takes a bunch of steps, and then at some point in the middle is going to look for a file that is of format filename<timestamp>.txt. If that file exists does something, if it doesn't don't do anything. I can get this to work by using the Get File Status and using the File Exists Published Data, but only if there actually is a file.
So if I setup Get File Status to look for filename*.txt and the file exists, everything runs smoothly, but if the file doesn't exist the object fails, instead of returning a File Exists value of false. I can setup my links to work off a failed status, but it makes it a harder to troubleshoot if a real failure occurs, as opposed to the file just not being there.
Does anyone know of a way to use wilcards in objects like Get File Status, where if the file is not present the object succeeds but returns a published data value of File Exists = false? The object works just like that when I use a static file name, it's only with the wildcards that I run into this issue. Thank you very much.
-NifflerX
All Replies
-
Tuesday, May 08, 2012 10:59 AMModerator
Hello NifflerX,
I consider that wildcards are not supported in Get File Status, see:
Get File Status
http://technet.microsoft.com/en-us/library/gg440659.aspxNo wildcard was mentioned in the document. However, if you check the "Copy File"(http://technet.microsoft.com/en-us/library/gg440773.aspx), "You can use the * and ? wildcards to specify the file name or path" is clearly indicated.
Thanks,
Yog Li
TechNet Community Support
- Proposed As Answer by StefanHorzMicrosoft Community Contributor Thursday, May 10, 2012 4:50 PM
- Unproposed As Answer by NifflerX Thursday, May 10, 2012 5:03 PM
-
Tuesday, May 08, 2012 1:54 PM
Hi,
Thank you very much for the response. I've tried using the Copy File object but the results are the same as the Get File Status, where if a file exists that matches the pattern it succeeds, but if not it fails. This actually makes a bit more sense to me than the Get File Status, since the object was unable to copy anything since there was nothing there to copy. But either way, it still leaves my logs full of failures and warnings even when the process hasn't actually failed. Does anyone have any other ideas on what to do when trying to branch on a file not there, without throwing a failure or warning? Thank you so much.
-NifflerX
-
Tuesday, May 08, 2012 4:02 PM
Hello,
you can configure the links. For example: After the "Get File Status" object. Condigutre this link ony to trigger if "File exists = true". Thefore click in the link to the name "Get File Status" and choose "File exits".
Best regards,
Stefan
- Proposed As Answer by StefanHorzMicrosoft Community Contributor Thursday, May 10, 2012 4:50 PM
-
Tuesday, May 08, 2012 6:05 PM
Thanks so much. Doing this worked in the sense that the workflow works correctly. I'm able get the work flow to work as expected. I actually have to use the Exclude section of the link as well, where I look to see if the number of files that would have been read is greater than zero. But, even though the workflow doesn't continue on it still logs as a failure since there was no file that matched the pattern, so when I go to look at the logs it still shows up with either a warning or an error. So the workflow works, which is the most important part, what I'm hoping to be able to do is get the log to be cleaner so when there are real errors it will be easier to go in and troubleshoot. Does anyone have any ideas on how I can do that? Thank you again for all the replies.
-NifflerX
-
Tuesday, May 08, 2012 7:45 PM
Hello,
which object(s) running with which conditions are causing the errors? Perhaps you can filter the condtion in the links that the obejcts get not executed ...
If you get an error with the "Get File"-Object if the file does not exist, I assume the OpalisIntegrationServer_FoundationObjects.msi are not installed correctly (location <install> \Opalis 6.3\Opalis Integration Server\). This OpalisIntegrationServer_FoundationObjects.msi must also replace the old version in folder C:\Program Files (x86)\Opalis Software\Opalis Integration Server\Management Service\Components\Objects. Otherwise when you deploy an Action Sever or Client the old version will be deployed again.
Best regards,
Stefan
-
Tuesday, May 08, 2012 7:48 PM
Hello,
sorry, I read that you use Opalis 6.22. For this are also updated Foundation Objects. The msi is placed in SP1 (placed in selfextracting OpalisServicePack1.exe).
Also here make shure to place the niewer version of OpalisIntegrationServer_FoundationObjects.msi in folder C:\Program Files\Opalis Software\Opalis Integration Server\Management Service\Components\Objects.
Before executing the OpalisIntegrationServer_FoundationObjects.msi you must first uninstall the old version with Control Panel/Add or Remove Programs
Good luck!
Stefan
German Orchestrator Portal , My blog in English
- Edited by StefanHorzMicrosoft Community Contributor Tuesday, May 08, 2012 7:52 PM
-
Tuesday, May 08, 2012 8:49 PM
Hi,
The error is coming when the Get File Status object is running and the file is not present. When I give the Get File Status object a static path to look for a file the object succeeds no matter if the file is there or not. If the file is there the "File Exists" status is true, otherwise it's false. However, if I give the Get File Status object a path with a wildcard, like C:\foo*.txt, then if the file doesn't exist I get a failure as opposed to a success with the "File Exists" status equal to false.
-NifflerX
-
Tuesday, May 08, 2012 9:03 PM
Hello,
do you use the updated Foundation Objects from Opalis6.22 SP1?
Regards,
Stefan
German Orchestrator Portal , My blog in English
- Edited by StefanHorzMicrosoft Community Contributor Tuesday, May 08, 2012 9:04 PM
-
Tuesday, May 08, 2012 9:44 PM
Hi,
I'm not sure. When I look at Control Panel > Programs and Features, the line item for Opalis Integration Server - Foundation Objects has version 6.3. Which is a little weird 'cause if I open up Opalis Integration Server and go to Help > About... it tells me the Client is version 6.2.2.5229. From that information can you tell if I'm using the updated Foundation Objects? Thanks.
-NifflerX
-
Wednesday, May 09, 2012 2:27 PM
Hi,
I think Version 6.3 should fit (I was expecting 6.2.2).
Do you have a different Action Server which is executing the Policies? Is an older version installed there?
Best regards,
Stefan
-
Wednesday, May 09, 2012 3:14 PM
Hi,
I've only got one action server and it was installed when everything was installed, but according the Programs and Features it is version 6.2.2. Is there a version 6.3 for Action Servers? Thanks again for all the help.
-NifflerX
-
Thursday, May 10, 2012 4:59 AM
Good Morning,
No. There's NO Update for Actions Servers provided in 6.3. Only Client, Management Server and Foundation Objects.
Please try to reinstall the Foundations Objects provides with 6.22 SP1 or with 6.3. "Get file Status" shoud finish green then if file not exists.
Regards,
Stefan
-
Thursday, May 10, 2012 1:21 PM
Hi,
Thanks for the reply. Just to be clear, if I give "Get File Status" a static path like C:\foo.txt and the file is not there, it does finish green, it's only if I give it a path like C:\foo*.txt that it will finish red. Given that would you still recommend a reinstall of the Foundations Objects? I'm not sure fixing this issue is a big enough deal for a reinstall. Thanks.
-NifflerX
-
Thursday, May 10, 2012 4:49 PM
Hi,
sorry, no same behavior here:
The green entry is a not existing file WITHOUT wildcard. The red is is the WITH wildcard.
Best regards,
Stefan
- Marked As Answer by NifflerX Thursday, May 10, 2012 5:04 PM
-
Thursday, May 10, 2012 5:03 PM
Hi,
Fair enough. I'll work around it for now. Using your examples of updating the links to route based no failure will work. Hopefully the process won't break too often so I won't have to worry about the log files. Thank you again for all your help with this.
-NifflerX

