How to use XML on another server?

Question

I need help figuring out how to consume XML from another
domain. It's a domain that is providing search functionality for a
website. The domain indexes my site, and I can "post" searches to
an URL with my search terms URL-escaped. It returns an XML
document. I want to use Spry to consume that XML.
I'm pretty experienced consuming XML and using it in Spry
pages, but to date have not done anything that crosses domains. I
will have access to Perl on the production box that hosts my site,
with a remote chance that I could get PHP enabled. This is a public
web server for a very very large financial company, so my choices
of what can go on a production server outside our firewall are
limited by corporate policy.
What are the basic steps that need to happen? Can someone
bullet-point how this might work from one end to the other? I have
the basic theory down of what needs to happen, but not much else at
this point.
Here is what I understand:
1 - user fills in search form and hits enter
2 - form posts to a Perl script on my box
3 - Perl takes the form variables and appends them to a URL
request to the 3rd party search domain
4 - 3rd party search company returns an xml file
5 - not sure what Perl needs to do here with the xml so that
my HTML page with Spry can read it....it does something, let's just
say
6 - Perl writes out a page, based on a template in my site
that then consumes the XML that is somehow available on my domain
now...
This raises so many questions...like if I save the results
XML on my server, how do I get rid of them after they are consumed
and also how do I prevent other sessions from accessing that "saved
copy" of XML...I know I'm thinking wrong here. That can't be how
it's done...Hence...my question about all this.
Where do I start?
Thanks,
Doug

Answer 1

user12004297 wrote:
thank you so much  -  however on the source database I dropped tables and users- then I  did an "alter system switch logfile;"  - copied the archivelogs to the / test  DRP and loaded the archivelogs and the users and tables were not dropped like i did in source
RMAN> tartup mount
Oracle instance started
database mounted
Total System Global Area    1119043584 bytes
Fixed Size                     2227624 bytes
Variable Size                620757592 bytes
Database Buffers             469762048 bytes
Redo Buffers                  26296320 bytes
RMAN> CATALOG START WITH '/oradb1/backup';
using target database control file instead of recovery catalog
searching for all files that match the pattern /oradb1/backup
List of Files Unknown to the Database
=====================================
File Name: /oradb1/backup/1_345_819727387.dbf
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /oradb1/backup/1_345_819727387.dbf
RMAN> recover database;
Starting recover at 20-NOV-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=249 device type=DISK
starting media recovery
media recovery complete, elapsed time: 00:00:02
Finished recover at 20-NOV-13
RMAN> alter database open;
database opened
RMAN
Simply making the database aware of the archivlogs does NOT mean rman will determine they need to be used for a specific recovery operation.  What all had you done to/with this database prior to this?   Keep firmly  in mind the effect of any OPEN RESETLOGS.