1. Library Control Interface (SCI) Reference Guide
  2. Preface

Preface

The StorageTek Library Control Interface (SCI) is a programmatic Web Services (SOAP) interface provided by the StorageTek SL4000 Modular Library System. Applications can use SCI to control the library. This document is intended for SCI developers.

WSDL URLs

Inbound SCI: http://<hostname>/WebService/1.0.0?wsdl

Outbound SCI: http://<hostname>/OutboundWebService/

Protocol Negotiation

You can connect to a base webservice (http://<hostname>/WebService/base?wsdl) that supports a single method: discover(). This method returns a list of supported web service protocols that the library understands. Use this method to ensure that the client code is compatible with the library. Currently there is only a 1.0.0 version WebService, which uses the SOAP 1.2 protocol.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documentation

Go to the Tape Storage section of the Oracle Help Center (https://docs.oracle.com/en/storage/tape-storage/index.html) for SL4000 documentation:

  • SL4000 Library Guide
  • SL4000 SCSI Reference Guide
  • SL4000 SCI Reference Guide
  • SL4000 Security Guide
  • SL4000 Safety and Compliance Guide
  • SL4000 Licensing Information User Guide

Diversity and Inclusion

Oracle is fully committed to diversity and inclusion. Oracle respects and values having a diverse workforce that increases thought leadership and innovation. As part of our initiative to build a more inclusive culture that positively impacts our employees, customers and partners we are working to remove insensitive terms from our products and documentation. We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.