MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Getting files into SPS 2003 Doc Libs

  Asked By: Angelique    Date: Jun 20    Category: MOSS    Views: 953

There must be many ways to do this, I am interested in knowing what
options exist.

We have a mainframe system that publishes many reports on a weekly,
monthly, quarterly basis. Some of these reports can become large (too
large to email). Currently, we burn the reports to CD-ROMS and stick
them in the mail to our remote employees. We are trying to think of a
way to better distribute the reports to the users as well as reduce

For now, we are planning to create a file-share on a server that the
mainframe will FTP the reports to. The share will have permissions set
for the appropriate users. Next, we are going to use a page-viewer
web-part (configured to the shared folder path) in SPS2003 to "viewport"
the folder to a WSS site. The users can then go and retrieve the
reports when they need them while the files themselves sit securely on
the file server (as opposed to living inside the SPS Content dB)

Question is, are there any other ways to get documents, reports, files
"INTO" a document library from outside of SsharePoint? Our requirements
above are pretty basic, so I was thinking the ftp/share method explained
was the lowest overhead. This is for SPS 2003 (although if there are
better mechanisms to accomplish this in MOSS2007 - I would love to hear
those as well)



3 Answers Found

Answer #1    Answered By: Anthony Rutledge     Answered On: Jun 20

You can map the doc  lib as a shared drive and put the content there if you want
to avoid using the Sharepoint UI but the content of the doc lib will still be
stored in a SQL DB.All content of sharepoint goes into a sql DB and you can also
back it up and your data will be secure.

I dont understand one thing (Out of curiosity) why you did not want the data in
a sql database.

Answer #2    Answered By: Heena Nagori     Answered On: Jun 20

Some of the reports include sensitive data that we wanted to further
secure with NTFS file-system as well security on access to the site.
Other reasons are that some of the reports are pretty big and we wanted
to maintain this on the file server instead of in the content dBs.
Also, the system that "generates" the reports uses FTP to deliver them -
I am not certain that it is possible to "ftp-enable" a document library
in SPS2003.

When you say, "you can map the doc  lib as a shared drive and put the
content in there" - this is manual operation from Windows Explorer... if
this can this be automated, so that the system (AS/400) generating the
reports can perform this start to finish, then yes this may be an

We are looking to automate this complete process, so that we build the
site, shares, configure ftp and configure the page viewer web-parts.
From there, the system should pretty much maintain itself without manual

Does this make sense? Thanks for your input, I would love to hear more
ideas on this...

Answer #3    Answered By: Aishwarya Karmarkar     Answered On: Jun 20

You can map it as a network drive in Windows and Copy it using dos commands in a
batch file which can be scheduled but i have never wroked on a main frame so nto
sure how it works.

Sharepoint server has different security leves such as read only and you can
also give security for different areas to different groups in a SPS 2003 portal
. Preety big report is how much big. If you can specify that some one on this
group will be able to tell you if they have tried storing such files  before.

Didn't find what you were looking for? Find more on Getting files into SPS 2003 Doc Libs Or get search suggestion and latest updates.