[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Rob Bruno asked, "Has anyone successfully exported records via TCP/IP to
their Innovative system using the new OCLC Connexion interface?"

Yes! As of this morning, we finally got it to work!

The first thing was realizing that the problem wasn't on OCLC's end.
Connexion was sending the bib records fine, but the receiving port on our
Innovative server (port 5500 for us) wasn't accepting them. So Connexion
would say "Record exported" with no error message, but the record would not
show up in our system.

Our Innovative server is not behind a firewall, but the "New TCP/IP Export
IP Address" message from Jim Simms at OCLC (forwarded to this list by Carol
Ritzenthaler under the subject header "RE: OCLC Connexion exporting")
provided us with the information we needed anyway. The numeric IP address
from which Connexion exports data is 132.174.2.67. (If your Innovative
server is behind a firewall, you might want to refer back to Jim Simms'
message for more details.)

This morning, the person with the deepest levels of access (the boss)
logged onto our Innovative server and went through the options: A>
Additional System Functions, A> Alter System Parameters, L> Login Names &
Parameters, N> Limit Network Access. There we chose the option for OCLCNET
(although I think this might be what we named it a long time ago, so the
option may be called something different on other systems), then added the
new IP. We used the same access and service levels as we'd used for earlier
options, and we didn't delete any other IPs, since we'll still be using
Passport for the bulk of our work for the near future.

Next when we tried exporting from Connexion, instead of the "Record
exported" message, we got a genuine error message. We were quite happy
about this, because it meant something real was happening. We went back
into our Connexion export options and changed the host name (our Innovative
server) to it's numeric IP form. The next export we tried went perfectly.

--Angela

=====
Angela Kroeger
akroeger@xxxxxxxxxx
University of Nebraska at Omaha Library, Monographic Cataloging