Constant Filepath :S:\SA\Bus_Activity\Records_Mgmt
[LL_Reptag_$filepath yyyyyy /]
Solving for yyyyy so that tag can read files on This location?
If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.
I'll let others comment on other ways to do this. As Appu mentioned Object Importer might be your best solution as it was designed for that kind of thing, but I can say that the sub-tags I previously mentioned (RB_FILEINFO and RB_FILEACTION) would achieve this. Unfortunately the External File data source or FTP data source are designed to pickup a single file that contains a table of items (in html or csv type format), similar to the results of a DB query. They are not designed to actually copy items from the location. We (my previous company that invented WebReports) did implement something called "pass thru" mode ([LL_WEBREPORT_PASSTHRU /]) that was originally designed to support this but we only got as far as allowing form data to be directly copied (without any special sub-tags) from source to destination.
The basic algorithm with our extended sub-tags would be something like the below; however, if you have layers and layers of folders, the algorithm would obviously be a bit more complicated, and with 18K files, might need to be partitioned in some way. FWIW, we also have a custom sub-tag that we share commercially that allows for a higher performance version of this. We can provide further information on that product or our free sub-tag suite via info@ravenblackts.com. We freely share the documentation for the sub-tag suite if you're interested.
Greg Petti
As Steve Jobs used to say: "there is an app for that". Actually a sub-tag or two. In our sub-tag suite we have FILEINFO, FILEACTION, and GETTEXTFILE Sub-tags. These jointly handle most file activities. There is some safety built into these by way of a concept of "path variables" that can be defined for custom file paths.
We have been making these sub-tags (and about 40 others) available to customers at no charge, albeit there are paid support packages available, and an additional tool that makes it easier to add, modify, and activate drop-in subtags.
info@ravenblackts.com
@GregPetti Thanks for the details. How can I use these tags? And are these capable of ingesting all files from that path?
Just curious, what does 'reading a file' mean? If your file is an Excel Spreadsheet having 8 worksheets, would you expect the WR to read worksheet 1 A1:A30 and so on… or is the intent to upload a file somewhere?
Good point Appu. The sub-tags can copy or move content from the file system, but the gettextfile sub-tag is purely designed to get text out of a text type file so you have the content to use in some way. The sub-tags do not provide a viewer, they are only a mechanism to access files.
Thanks Greg. My post was to the OP, in OT circles, Object Importer is the tool of choice, along with a myriad of options of ingesting files using SOAP, REST, and so on. Perhaps this is a user who is good at SQL and WR and wants to consume files that way. I know of one file system action created by a user in WR
https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=76455857&objAction=viewincontainer&ShowReplyEntry=76980600
However, at the time of the posting, Chris Webster, who we all know is kind of A LEGEND, commented that when you allow file system access through WR(Oscript) one is also inviting trouble unless it is security constrained not to compromise the server. Another aspect that I noticed while working on the K8s(Kubernetes Version) is that the file system is kind of difficult for the pods(Yes, I know PVC).
In reality, the Post says "Read Files" which I interpreted as reading line by line content and doing something with it, which would mean one would need some kind of application api's embedded as well.
We typically don't use these sub-tags for the same use cases as object importer, though we have created a migration engine in the past, using this functionality where we are also potentially creating new CS objects and manipulating them with WR actions etc. - very flexible! Besides migration, there are actually dozens of use cases where checking file information, copying files, creating objects from files, or whatever are useful. Many customers and partners are using WR to create fully functioning, meaningful applications (including us) and to do that you need the full capability you would have with any development tool. Also, as with all development capability, there is the potential for creating trouble. Given that everything done with WebReports requires an authenticated user working through auditable, permissioned objects, the security is actually higher than many alternatives. Of course the best way to avoid compromising any server is not to allow anyone to do anything that would modify the core functionality, but that is not the world we live in, and all capability provided for development has the potential for trouble whether malicious or accidental. The objective when creating tools like this is to provide as much capability as possible with sensible safeguards built in. With these file sub-tags we did various things to restrict who can actually use them in a WebReport to limit the scope of people who can set them up, but we also wanted to reduce the possibility that a validly authenticated developer might accidentally damage something so we have a system of path variables that have to be setup using a separate tool in order to define what these sub-tags can actually access. This is similar to the restrictions imposed by core WebReports for file paths, and we will likely leverage those paths in the future too.
Finally, one of our objectives as a company is to help customers to achieve maximum development potential, while using all these tools safely and as they were designed to be used.
Cheers
Greg
As mentioned by Appu, I am more comfortable using the Webreport and sql. Hence was wondering if there is a way to pick files up from the location and uplaod them to OTCS. The problem scenarios: 18k files present in boxes, that need to be traversed, and the files need to be picked up and uploaded into OTCS with metadata matching its name based on metadata sheet. Source1 : Metadata sheet uploaded in OTCS
WR 1: Reading from above source.
SubWebreport: Expecting to read files using FTP source function and uploading them to OTCS. The above might not be the best way to tackle the problem. If there is any other suggestion, happy to take that.
Also location is within the OTCS Admin server where those files are located.
RB_FILEACTION
I believe the above is the tag that I am looking for. On another note, Ot just got back to me with details on the restclient tag, they said that they intended it be used on other external systems and it may be unreliable if it is calling on the RestAPi of the OTCS it is hosted on. The underlying reason of doing all this via webreport is that we would like to host most of our code in OTCS itself rather than maintain repositories outside.
I wish the other company would have completed that PassThru, it would have been powerful tag and would have eliminated a lot of code that we do for drop boxes and uploads in OTCS
