NonStop SOAP for Java User’s Manual Abstract This manual provides reference and user information for NonStop™ SOAP for Java, a product that runs on a Compaq NonStop server and provides Simple Object Access Protocol (SOAP) access to NonStop Java classes and NonStop Enterprise Java Bean (EJB) environments. Product Version NonStop SOAP for Java Release 1.0 Supported Releases NonStop SOAP for Java is compatible with the Compaq NonStop Kernel G06 release version update (RVU) and subsequent RVUs.
Document History Part Number Product Version 523860-001 NonStop SOAP for Java 1.
NonStop SOAP for Java User’s Manual Glossary Index What’s New in This Manual v Manual Information v New and Changed Information Examples Figures v About This Manual vii Prerequisites vii Your Comments Invited viii Notation Conventions ix Abbreviations xiii 1.
. SOAP Deployment Descriptor Contents 4. SOAP Deployment Descriptor Deployment Descriptors 4-1 SOAP to Java Class Deployment Descriptor 4-1 SOAP to EJB Deployment Descriptor 4-3 Specifying Type Mapping in a Deployment Descriptor File Fault Handling 4-8 Registering Fault Handlers 4-8 Creating New Fault Handlers 4-8 4-5 5.
7. Samples Deploying NonStop SOAP for Java Contents 7. Samples Deploying NonStop SOAP for Java Deploying a Java Class as a Web Service 7-1 Deployment Using NskSoapManager 7-2 Deployment Using Apache SOAP Admin 7-2 8. Troubleshooting Tips for NonStop for Java What to Do if You Can’t Solve a Problem 8-1 What to Do if the Samples Don’t Work 8-1 What to Do if the Tools in the bin Directory Don’t Run 8-2 A. Locating the ContextProviderURL Glossary Index Examples Example 4-1. Example 4-2. Example 4-3.
Contents NonStop SOAP for Java User’s Manual—523860-001 iv
What’s New in This Manual Manual Information NonStop SOAP User’s Manual Abstract This manual provides reference and user information for NonStop SOAP for Java, a product that runs on a Compaq NonStop server and provides Simple Object Access Protocol (SOAP) access to NonStop Java classes and NonStop Enterprise Java Bean (EJB) environments. NonStop SOAP for Java allows Java-based services to be made available in a Web services environment. Product Version NonStop SOAP for Java Release 1.
What’s New in This Manual New and Changed Information NonStop SOAP for Java User’s Manual—523860-001 vi
About This Manual This manual describes NonStop SOAP for Java, a product that runs on a Compaq NonStop Himalaya S-series server and provides Simple Object Access Protocol (SOAP) access to NonStop Java classes and NonStop Enterprise Java Bean (EJB) environments. NonStop SOAP for Java allows Java-based services to be made available in a Web services environment. • • • • • • • • Section 1, Introduction to NonStop SOAP for Java, describes the features and architecture of NonStop SOAP for Java.
Related Compaq Products About This Manual • Extensible Markup Language (XML) http://www.w3.org/TR/REC-xml • Simple Object Access Protocol (SOAP) http://www.w3.org/TR/SOAP • Simple Object Access Protocol (SOAP) with Attachments http://www.w3.org/TR/SOAP-attachments • Web Services Description Language (WSDL) http://www.w3.org/TR/WSDL.html • Apache SOAP version 2.2 http://www.apache.org/soap/index.
Notation Conventions About This Manual Many of the improvements you see in manuals are a result of suggestions from our customers. Please take this opportunity to help us improve future manuals. Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2.
General Syntax Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Notation for Messages About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]… !i and !o.
Notation for Messages About This Manual Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
Abbreviations About This Manual NonStop SOAP for Java User’s Manual—523860-001 xiv
1 Introduction to NonStop SOAP for Java NonStop SOAP for Java runs on a NonStop server and allows a Simple Object Access Protocol (SOAP) client to communicate with NonStop Java classes and NonStop Enterprise Java Beans (EJB) as shown in Figure 1-1. NonStop SOAP for Java allows Java-based services to be made available in a Web services environment. Figure 1-1.
Introduction to NonStop SOAP for Java Brief Introduction to Web Services Brief Introduction to Web Services A Web service is a collection of functions that are packaged as a single-entity and published to the network for use by other programs.
Introduction to NonStop SOAP for Java Creating a NonStop Web Service for Java 2. Deploy. To deploy a component as a Web service you must describe the component and associated configuration to the NonStop Web service infrastructure Administration tool, NskSoapManager. You can also use the Apache Admin tool. You use the Administration tools to create and deploy the SOAP deployment descriptor file. See Using the Administration Tools on page 5-1. 3. Invoke.
Introduction to NonStop SOAP for Java Features and Functions of NonStop SOAP for Java Features and Functions of NonStop SOAP for Java NonStop SOAP for Java includes: • • • • • • • A configuration file and setup script to install NonStop SOAP for Java under the iTP WebServer and NSJSP environments. See Configuring NonStop SOAP for Java on page 3-1. A deployment descriptor file that exposes a service implemented using a standard Java class (including a normal Java bean) or an Enterprise Java Bean (EJB).
Introduction to NonStop SOAP for Java Web Service Provider Web Service Provider The Web Service Provider acts as a bridge between the web service engine and the end-point that provides the service. NonStop SOAP for Java has the following providers: • • Java provider—which allows you to expose Java classes. Enterprise Java Bean (EJB) provider—which allows you to expose EJB (stateless, stateful, or entity beans.
Introduction to NonStop SOAP for Java Prerequisite Software Prerequisite Software • • • • • • • NonStop Kernel Operating System (G06 or later) OSS (T8620) installed and running Transaction Monitoring Facility (TMF) of NonStop TMF installed and running NonStop Server for Java (NSJ) version 1.2.2 (IPM AAG or later) installed and running iTP WebServer version 5.0 installed and running NonStop Servlets for JavaServer Pages (NSJSP) version 1.0 NonStop Enterprise Application Server (EAS) version 1.
2 Installing NonStop SOAP for Java The NonStop SOAP for Java CD includes: • NonStop SOAP for Java This section describes how to install NonStop SOAP for Java. For information about installing iTP Webserver and NonStop Servlets for JavaServer Pages (NSJSP), see the documentation for those products. Copying the Software from the CD Consult the NonStop SOAP for Java softdoc for last-minute changes to the installation instructions given here.
Installing NonStop SOAP for Java • • • • • • • activation.jar. This JAR file contains the classes that make up JavaBeans Activation Framework. nssoap.jar. This JAR file contains NonStop SOAP for Java specific classes. /samples—Contains • • NonStop SOAP for Java Directory Structure .java and .class files. The .java files contain the code for the SOAP client and the SOAP service including some helper classes. Samples like SOAP-EJB, contain just the SOAP client files. The .
3 Configuring NonStop SOAP for Java This section describes how to configure NonStop SOAP for Java. Before you configure NonStop SOAP for Java, you must do the following: • • Install and configure the iTP WebServer as described in the iTP Secure WebServer System Administrator’s Guide. NonStop SOAP for Java does not require the secure version of the iTP WebServer, but that manual describes installation and configuration for all versions of the iTP WebServer.
Configuring NonStop SOAP for Java Run the Setup Script After doing these steps, the setup script prompts you to make changes at specific locations in the file usr/tandem/webserver/conf/servlet.config. These changes are shown in Steps 4 & 5 (typical values). 4. Using the editor of your choice, modify the /usr/tandem/webserver/conf/servlet.config file as follows: a.
4 SOAP Deployment Descriptor This section describes how to expose a Web service by using deployment descriptors. Deployment descriptors are an integral part of the Java 2 Platform Enterprise Edition (J2EE) Web applications. Deployment descriptors help manage the configuration of Web applications once the Web applications are deployed.
SOAP Deployment Descriptor SOAP to Java Class Deployment Descriptor checkMustUnderstand attribute This attribute is either true or false. If true, the server must be able to throw a fault when the SOAP message has headers marked as MustUnderstand. This attribute is optional. isd:provider type attribute This attribute designates the language to be used. isd:java class attribute The fully-qualified name of the Java class that implements the service. For example, packagename.classname.
SOAP Deployment Descriptor SOAP to EJB Deployment Descriptor SOAP to EJB Deployment Descriptor Example 4-2 shows a deployment descriptor file that exposes a service implemented using an Enterprise Java Bean (EJB). Example 4-2. Deployment Descriptor File (SOAP to EJB) PAGE 30SOAP Deployment Descriptor SOAP to EJB Deployment Descriptor Application the object lasts until the servlet that is servicing the requests is terminated. isd:provider methods attribute This attribute is a list of names of methods that the service implements. The list items are separated by spaces. This attribute has the same meaning as in the standard Java class deployment descriptor. isd:option key attribute The jndi-name is the registered JNDI name of the EJB.
SOAP Deployment Descriptor Specifying Type Mapping in a Deployment Descriptor File Specifying Type Mapping in a Deployment Descriptor File Each type of variable is transmitted to a server by a SOAP message must be translated from XML to Java primitive or reference variable and, in turn, variables returned by the RPC must be encoded from Java into XML. Selecting the right method for a conversion is accomplished by “type mapping” data.
SOAP Deployment Descriptor Specifying Type Mapping in a Deployment Descriptor File isd:map encodingStyle attribute is the URI for the encoding method. For standard SOAP encoding: http://schemas.xmlsoap.org/soap/encoding. isd:map xlmns:x attribute is the namespace for the XML element. isd:map qname attribute is the name of the XML element. isd:map java-type attribute is the fully qualified Java class that you are providing the mapping for (for example, samples.Date,).
SOAP Deployment Descriptor Specifying Type Mapping in a Deployment Descriptor File For example, the following deployment descriptor can be seen in the Address Book sample. The mappings are provided under the element as a separate element for each mapping provided. Example 4-4. Example Deployment Descriptor PAGE 34SOAP Deployment Descriptor Fault Handling Fault Handling Occasionally, an error occurs on the server side. It could be a bad service implementation, a bad client request, or normal operating difficulties. The SOAP specification provides for the communication of these errors through the transmittal of a SOAP Fault body element within a SOAP Envelope. The SOAP server tries to capture an error state and then construct a SOAP Fault message containing a base set of information about the error.
5 Using the Administration Tools This section describes how to use the Administration tools. The Administration tools enables you to deploy a Web service. The Administration tools are Java-based tools that provide administrative functions to deploy a Web service. You invoke the Administrative tools through a command-line or web-based interface. The tools deploy automatically when started in Java mode or EJB mode.
Using the Administration Tools Using Java Mode Using Java Mode In Java mode, NskSoapManager assists you in exposing and deploying the methods of a Java class which is locatable by using the program’s CLASSPATH. Note. Before starting the NskSoapManger tool, verify that the class to be deployed is in the CLASSPATH. Also, verify that you have sourced the env.sh file located in the /usr/tandem/nssoap/T2764V10/etc directory. 1. Use these commands to start the NskSoapManager tool in Java mode.
Using the Administration Tools • • • Using Java Mode A URI name for the service A target server for the SOAP binding A file name to which the WSDL will be written a. Each service to be deployed needs a URI name. NskSoapManager prompts you to specify a URI name as follows: /***********************/ Creating WSDL Files /***********************/ Enter a URI name for the class ‘java.lang.Object’ [urn:Object]: To select the NskSoapManager generated URI name, press Enter.
Using the Administration Tools Using Java Mode To select the NskSoapManager generated file name, press Enter. To write to a specific file, enter the name and location of the target file. If the file exists, its contents are overwritten. ******* Creating Deployment Descriptors ******** Values in [] indicate default values. Press enter to accept the default values or enter a new value at the prompt Enter a deployment descriptor file name for the class ‘java.lang.Object’ [Object_DD.
Using the Administration Tools Using EJB Mode Using EJB Mode In EJB mode, the NskSoapManager tool assists you in exposing and deploying the methods of multiple NSEJBs contained in a .jar file. Given the location of the NSEJB .jar file name, NskSoapManager generates a SOAP deployment descriptor and a WSDL file as an output for each EJB selected to be deployed from the .jar file. NskSoapManager can register the service with the SOAP server. Note.
Using the Administration Tools Using EJB Mode If the selection is invalid, an error is displayed and you are given the option to retry or exit. Once a valid selection is made, you must confirm the selection and proceed, or go back and re-select the EJBs.
Using the Administration Tools Using EJB Mode For example, continuing with the selection of EJBs, you receive the following screens: The ComputationEngineBean has the following methods: Method[0] = compute Select the methods that you want to expose in the SOAP service: 0 The PlayerSessionBean has the following methods: Method[0] = bet Method[1] = getAvailableMachines Method[2] = selectMachine Method[3] = signOff Method[4] = signOn Method[5] = unSelectMachine Method[6] = create Select the methods that you
Using the Administration Tools Using EJB Mode Once all the URI names are entered (default or user-specified), you must confirm the selection or re-specify each URI name. /***********************/ Creating WSDL Files /***********************/ Enter a URI name for the EJB named ComputationEngineBean[urn:ComputationEngineBean]: Enter a URI name for the EJB named PlayerSessionBean[PlayerSessionBean]: Enter a URI name for the EJB named Player Bean[urn:PlayerBean]: b. Specify a target server.
Using EJB Mode Using the Administration Tools Once all the file names are entered (default or user-specified), you must confirm their selection or re-specify each file name. ******* Creating Deployment Descriptors ******** Values in [] indicate default values. Press enter to accept the default values or enter a new value at the prompt Enter deployment descriptor file name for the EJB named ComputationEngineBean[ComputationEngineBean_DD.
Using the Administration Tools Using EJB Mode The default value of the server is the value that was entered in Step 4. After attempting to deploy, NskSoapManager writes the contents of the deployment descriptor to the file name specified in Step 5. Deploy ComputationEngineBean?? [Y to deploy, any other key to continue]: n Skipping deployment. Writing the Deployment Descriptor details to ComputationEngineBean_DD.xml ........
Using the Administration Tools Using the Apache Admin Tool Using the Apache Admin Tool Apache SOAP also provides an Administration tool to manage services. Two clients are available to manage services: a web-based version using a browser and a command-line tool.
Using the Administration Tools Using the Apache Admin Tool (Web-Based) Figure 5-1. Apache SOAP Admin Screen Service Deployment Information This section describes the information you must provide to deploy a service. Provide the following information when you use the Deploy function. You can list this information by using the List function. This information is referred as properties of the service. • • ID—An URN uniquely identifies the service to clients.
Using the Administration Tools • • • • • • • • • • Using the Apache Admin Tool (Web-Based) page: the object is available until the target JSP page (in this case, the rpcrouter.jsp) sends a response back or the request is forwarded to another page (if you are using the standard deployment mechanism this is unlikely to happen). request: the object is available for the complete duration of the request, regardless of forwarding. session: the object is available for the complete duration of the session.
Using the Administration Tools Deploying EJB Applications as Web Services descriptor, this can be specified in a defaultRegistryClass attribute of the isd:mappings element. Deploying EJB Applications as Web Services This section discusses the deployment of NonStop EJB applications as Web services using the web-based Apache Admin tool. Also needed for successful deployment is a value called ContextProviderURL.
Using the Administration Tools Deploying EJB Applications as Web Services Figure 5-2. Apache SOAP Admin—Deploying an EJB Application Types of Enterprise Beans The two types of enterprise bean types are: Session Beans and Entity Beans. Session Beans A session bean is similar to an interactive session. A session bean is not shared—it can just have one client, in the same way that an interactive session has just one user. Like an interactive session, a session bean is not persistent.
Using the Administration Tools Deploying EJB Applications as Web Services Entity Beans An entity bean represents an entity kept in a persistent storage mechanism, usually a database. A business application, for example, might use a database to store business entity objects such as accounts, customers, orders, and products. Inside the NonStop EJB application server, this application would represent the business entity objects with entity beans. Entity beans differ from session beans in several ways.
Deploying a Stateless Session Bean Using the Administration Tools Deploying a Stateless Session Bean Table 5-1 deploys a stateless session bean called TranslatorBean which is a sample provided with the NSEJB product. Type the following information in the form (refer to the Apache SOAP Admin Screen on page 5-12. Table 5-1. Deploying Stateless Session Bean ID urn:Translator Scope Application Methods translate Provider Type User-Defined FULL Class Name com.tandem.soap.providers.
Deploying a Stateful Session Bean Using the Administration Tools • Option 3: Key : ContextProviderURL Value : corbaloc://ip-address-of-NSK-system:ILSD_port (see Appendix A, Locating the ContextProviderURL) • Option 3: Key : FullContextFactoryName Value : com.tandem.nsdom.jndi.CosNaming.CNContextFactory (This value is fixed and defines the Context Factory class to use for JNDI lookups for NSEJBs.
Deploying an Entity Bean Using the Administration Tools Deploying an Entity Bean Table 5-3 deploys an entity bean called the AccountBean (CMP) which is a sample provided with the NSEJB product. Type the following information in the form. Table 5-3. Deploying an Entity Bean ID urn:CMPAccount Scope Application Methods debit credit getBalance create findByPrimaryKey Provider Type User-Defined FULL Class Name org.apache.soap.providers.
Deploying an Entity Bean Using the Administration Tools First Request SOAP Message Example 5-1 deploys a stateful session bean and shows the "create" method being invoked. . Example 5-1. First Request SOAP Message POST /servlet_jsp/soap-2_2/servlet/rpcrouter HTTP/1.0Host: localhost Content-Type: text/xml; charset=utf-8 Content-Length: 447 SOAPAction: "" PAGE 55Using the Administration Tools Deploying an Entity Bean First Response SOAP Message Example 5-2 shows the SOAP response to the "create" method response. Example 5-2. First Response SOAP Message HTTP/1.1 200 Date: xxxxxxx Server: iTP Secure WebServer/5.0 MIME-version: 1.0 Connection: close Content-Length: 1811 Servlet-Engine: iTP WebServer with NonStop Servlets and JSP/1.0 (JSP 1.1; Servlet 2.2; Java 1.2.2; NONSTOP_KERNEL G06 mips; java.vendor=Compaq Computer Inc.
Deploying an Entity Bean Using the Administration Tools Second Request SOAP Message Example 5-3 shows the "addItem" method being invoked. Example 5-3. Second Request SOAP Message POST /servlet_jsp/soap-2_2/servlet/rpcrouter HTTP/1.0Host: localhost Content-Type: text/xml; charset=utf-8 Content-Length: 1844 SOAPAction: "" Cookie: JSESSIONID=$Z86L$nz072cz8o1 Cookie2: JSESSIONID=$Z86L$nz072cz8o1 PAGE 57Deploying an Entity Bean Using the Administration Tools Second Response SOAP Message Example 5-4 shows the response to the "addItem" method response. Example 5-4. Second Response SOAP Message HTTP/1.1 200 Date: xxxxxx Server: iTP Secure WebServer/5.0 MIME-version: 1.0 Connection: close Content-Length: 1813 Servlet-Engine: iTP WebServer with NonStop Servlets and JSP/1.0 (JSP 1.1; Servlet 2.2; Java 1.2.2; NONSTOP_KERNEL G06 mips; java.vendor=Compaq Computer Inc.
Using the Administration Tools Using the Apache Admin Tool (Command-Line) Using the Apache Admin Tool (Command-Line) The Apache SOAP Admin tool also provides a command-line tool to manage services. oss> java org.apache.soap.server.ServiceManagerClient [-auth username:password] url operation arguments where username and password is the HTTP Basic authentication information. url is the SOAP server's URL. operation and (arguments to the operation) The values are: • • • • deploy deployment-descriptor-file.
Using the Administration Tools Tracing SOAP Messages Tracing SOAP Messages NonStop SOAP for Java has two options available for tracing SOAP messages: • • Using Command-Line Based Tcp Tunnel on page 5-25 Enabling Server-Side Tracing on page 5-25 Using Command-Line Based Tcp Tunnel This is a command-line based tool version of Tcp Tunnel. It can open a port on the machine on which it was started, and will tunnel traffic to the remote host/port combination. You need to provide a file name at startup.
Using the Administration Tools Enabling Server-Side Tracing Verify that the rpcrouter servlet has the following init parameter TraceFile /usr/tandem/nssoap/T2764V10/soap4java.trc param-name must be TraceFile. param-value is the name (and path) of the user-desired trace file. By default, tracing is turned off.
Using the Administration Tools Additional Tools Additional Tools This section describes additional tools that can be used with the NonStop SOAP for Java product. The NonStop SOAP for Java tools are placed in the bin directory. The tools are: • deploy. This tool deploys a service. deploy • undeploy. This tool undeploys a service.
Using the Administration Tools NonStop SOAP for Java User’s Manual—523860-001 5- 28 Additional Tools
6 Using the SOAP Client APIs This section discusses the SOAP client-side APIs for Java and how attachments are implemented on the client and server. Note. The NonStop SOAP for Java client-side APIs product and documentation is based on the Apache SOAP version 2.2 specification. The Apache SOAP User’s Guide is available at http://xml.apache.org/SOAP/docs/guide/intro.html.
Interacting with Stateful Services Using the SOAP Client APIs This method must be one of the methods exposed by the service identified by the URN given in the previous step. 6. Create any Parameter objects necessary for the RPC call and set them into the Call object using the setParams(...) method. Verify that you have the same number of parameters that have the same types as the service is expecting.
Using Attachments Using the SOAP Client APIs Using Attachments This section describes SOAP messages with attachments. The SOAP messages with attachments proposal has been published as a W3C Note at http://www.w3.org.TR/SOAP-attachments. In this scheme, the MIME (Multipurpose Internet Mail Extensions) multipart message format is used to bundle a complete standard SOAP message with additional data in a “SOAP message package.
Using Attachments on the Server Using the SOAP Client APIs Using Attachments on the Server As in the client case, if you are implementing an RPC-based service you may be able to take advantage of the built-in serializers/deserializers for the javax.activation.DataSource and javax.activation.DataHandler objects. If you are implementing a message-oriented service, you can use methods from the following class to add or retrieve MimeBodyParts: org.apache.soap.rpc.
7 Samples Deploying NonStop SOAP for Java The NonStop SOAP for Java samples are located under the following directory: /usr/tandem/nssoap/T2764V10/samples An individual sample may consist of a number of .java and .class files contained in a separate child directory under the samples directory. The individual directories contain: • • • • DeploymentDescriptor.xml: An XML file containing the deployment descriptor for that sample. Most of the samples can be run using this deployment descriptor unchanged.
Samples Deploying NonStop SOAP for Java Deployment Using NskSoapManager Deployment Using NskSoapManager To deploy using NskSoapManager, you need to follow the steps listed in Section 5, Using the Administration Tools on running the NskSoapManager tool. Verify that the class you want to deploy is locatable in the CLASSPATH with which the tool is started.
Samples Deploying NonStop SOAP for Java • • • Deployment Using Apache SOAP Admin Class Name: com.myfirm.product.classToDeploy Methods: method1, method2, method3 Methods to be exposed: method1, method3 In Table 7-1, fill-in the information appearing in the following form in the appropriate fields in the screen: Table 7-1. Sample Form ID urn:DeployedClass Scope Application Methods method1 method3 Provider Type Java FULL Class Name Number of Options 4 Key Java Provider Provider Class com.
Samples Deploying NonStop SOAP for Java Deployment Using Apache SOAP Admin 2. In a .class file: If the classToDeploy.class is present under a directory structure (com/myfirm/product/), then copy the entire "com" directory to the /servlet_jsp/webapps/soap/WEBINF/classes directory. Assuming default values, if the Context entry in the /servlet_jsp/conf/iTP_server.
8 Troubleshooting Tips for NonStop for Java This section provides NonStop SOAP for Java troubleshooting tips and identifies common problems. It also explains general troubleshooting concepts related to NonStop SOAP for Java. A good understanding of Java and normal operation of your system are the most crucial elements in problem resolution. You should have a thorough understanding of the material presented in that manual before attempting to resolve any NonStop SOAP for Java problems.
Troubleshooting Tips for NonStop for Java • What to Do if the Tools in the bin Directory Don’t Run Verify that you source in the contents of the following file: /usr/tandem/nssoap/T2764V10/etc/env.sh This file contains necessary environment variables required for the samples to run correctly • • • Verify that after installation that you have restarted the iTP WebServer. Verify that the value of the URL variable in the run.
A Locating the ContextProviderURL To successfully deploy EJB applications as Web services, you need a value called ContextProviderURL for the user-specific NSEJB installation. To locate the value of ContextProviderURL you must do the following: 1. Launch the NonStop Console from the NonStop Console icon on the desktop if you installed the Console with the default installation. Double-click the icon. The console main panel comes up. 2.
Locating the ContextProviderURL . Figure A-1.
Locating the ContextProviderURL Click the button shown immediately below; the NonStop (TM) Distributed Components Console Figure A-2 appears. Figure A-2.
Locating the ContextProviderURL Click the button shown immediately below; then click the ILSD tab; the ISDL Server Configuration dialog Figure A-3 appears. Figure A-3. ILSD Server Configuration The value for ContextProviderURL is corbaloc://16.107.100.51:2811 (which is obtained by using the values of Host address and Port number.
Glossary attribute. An item of descriptive data associated with an XML element. An attribute has a name and a value. bean. See Java bean. Document Type Definition (DTD). A specification of valid syntax for a class of XML documents. A DTD specifies required elements and attributes, and permissible and default values of attributes. DTD. Document Type Definition. child.
fault. Glossary fault. An error condition reported by a SOAP server in response to a request. Hypertext Transport Protocol (HTTP). The set of rules (protocols) based on TCP/IP that provides the foundation for communication between web clients and servers. internationalization. Provision for conversion of data to the encoding a client requires. JAR (Java ARchive). File format similar to Zip for collecting multiple resources (such as class files and Java class libraries) in a single file.
Open System Services (OSS). Glossary by identifying the namespace expresses the idea that the name is used as defined in that namespace. Open System Services (OSS). Himalaya systems. A POSIX-compliant operating environment for NonStop parent. In a hierarchical system, any class that is the ancestor of another class. OSS. Open System Services remote procedure call (RPC). The general term for executing a method on an application that resides on another system by means of some communication protocol. RPC.
unmarshal. Glossary unmarshal. To deserialize a data stream to create a C++/Java object, for example, to convert an XML document into a C++ object. Uniform Resource Identifier (URI). The generic set of all names and addresses that refer to resources. URI. See Uniform Resource Identifier. Web Application Resource (WAR). A collection of all files needed to create a web application in a single file using the Zip compression algorithm. Specified in the servlet 2.2. API.
Index A Administration tools 5-1 Apache client-side APIs 6-1 command line tool 5-24 web browser tool 5-11 Apache SOAP 1-1 Attachments client 6-3 referencing 6-4 server 6-4 Deployment descriptor type mapping 4-5 doc directory 2-1 E Enterprise Java Beans 1-1 etc directory 2-2 Examples links to 4-5 F Fault handlers creating 4-8 registering 4-8 Fault handling 4-8 B bin directory 2-1 C H CD copying software from 2-1 software products included on 2-1 Configuring and running the server in a WebServer enviro
L Index Java Servlet API version 1-6 Prerequisite software 1-4 R L Registering fault handlers 4-8 Running server in WebServer environment 3-1 lib directory 2-1 N NonStop 2-1 NonStop EAS 1-6 NonStop Kernel version 1-6 NonStop Server for Java (NSJ) 1-6 NonStop Servlets for JavaServer Pages 1-6, 3-1 NonStop SOAP for Java administration tools 1-4 architecture 1-4 attachments 1-4 client-side APIs 1-4 configuring 3-1 deployment descriptor 1-4 directory structure 2-1 features 1-4 features and functions 1-4
X Index X XML version 1-6 NonStop SOAP for Java User’s Manual—523860-001 Index -3
X Index NonStop SOAP for Java User’s Manual—523860-001 Index -4
