ptc官網(wǎng)資料windchill相關(guān)資料ptc官網(wǎng)資料-1_W

1、SAP Adapter GuidePTC Windchill 11.0 F000Copyright 2015 PTC Inc. and/or Its Subsidiary Companies. All Rights Reserved.User and training guides and related documentation from PTC Inc. and its subsidiary companies (collectively PTC) are subject to the copyright laws of the United States and other count

2、ries and are provided under a license agreement that restricts copying, disclosure, and use of such documentation. PTC hereby grants to the licensed software user the right to make copies in printed form of this documentation if provided on software media, but only for internal/personal use and in a

3、ccordance with the license agreement under which the applicable software is licensed. Any copy made shall include the PTC copyright notice and any other proprietary notice provided by PTC. Training materials may not be copied without the express written consent of PTC. This documentation may not be

4、disclosed, transferred, modified, or reduced to any form, including electronic media, or transmitted or made publicly available by any means without the prior written consent ofPTC and no authorization is granted to make copies for such purposes.Information described herein is furnished for general

5、information only, is subject to change without notice,and should not be construed as a warranty or commitment by PTC. PTC assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.The software described in this document is provided under written license a

6、greement, contains valuable trade secrets and proprietary information, and is protected by the copyright laws of the United States and other countries. It may not be copied or distributed in any form or medium, disclosed to third parties, or used in anymanner not provided for in the software license

7、s agreement except with written prior approval from PTC.UNAUTHORIZED USE OF SOFTWARE OR ITS DOCUMENTATION CAN RESULT IN CIVILDAMAGES AND CRIMINAL PROSECUTION. PTC regards software piracy as the crime it is, and we view offenders accordingly. We do not tolerate the piracy of PTC software products, an

8、d we pursue (both civilly and criminally) those who do so using all legal means available, including public and private surveillance resources. As part of these efforts, PTC uses data monitoring and scouring technologies to obtain and transmit data on users of illegal copies of our software. This da

9、ta collection is not performed on users of legally licensed software from PTC and its authorized distributors. If you are using an illegal copy of our software and do not consent to the collection and transmission of such data (including to the United States), ceaseusing the illegal version, and con

10、tact PTC to obtain a legally licensed copy.Important Copyright, Trademark, Patent, and Licensing Information: See the About Box, or copyrightnotice, of your PTC software.UNITED STATES GOVERNMENT RESTRICTED RIGHTS LEGENDThis document and the software described herein are Commercial Computer Documenta

11、tion and Software, pursuant to FAR 12.212(a)-(b) (OCT95) or DFARS 227.7202-1(a) and 227.7202-3(a) (JUN95), and areprovided to the US Government under a limited commercial license only. For procurements predating the above clauses, use, duplication, or disclosure by the Government is subject to the r

12、estrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software Clause at DFARS 252.227- 7013 (OCT88) or Commercial Computer Software-Restricted Rights at FAR 52.227-19(c)(1)-(2) (JUN87),as applicable. 01012015PTC Inc., 140 Kendrick Street, Needham, MA 02494 US

13、AContentsAbout This Guide5Info*Engine Architecture9Identifying the Info*Engine Components10Identifying Basic Components11Interacting with Info*Engine11Managing the Execution of Info*Engine Tasks16Starting and Locating Info*Engine Components23Setting Up Connections Through Adapters25SAP Adapter Archi

14、tecture28SAP Adapter Installation29Installation Overview and Requirements30Installing the SAP Adapter31SAP Adapter Configuration33Configuring an In-Process SAP Adapter34Configuring an Out-of-Process SAP Adapter34Creating the SAPAdapter LDAP Entry38SAP Adapter Properties42SAP Webject Library47Naming

15、the Adapter in INSTANCE Parameters48Commit-Transaction50End-Transaction51Execute-RFC53Rollback-Transaction60Start-Transaction62Transaction Management Example64Directory Structures713About This GuideThis SAPAdapter Guide documents the use of the PTC Info*Engine SAP adapter software and assumes you ar

16、e familiar with the basics of HTML, XML, and JSP as defined by the World Wide Web Consortium ().To take advantage of the advanced functionality of Info*Engine, you must have expert knowledge of HTML, XML, and JSP.Related DocumentationThe following documentation might be helpful:The

17、PTC Windchill Installation and Configuration Guide details the procedure for installing and configuring Windchill. Info*Engine is installed alongside Windchill as a bundled component.The Info*Engine Users Guide details the main functionality of the Info*Engine server.The Info*Engine Java Adapter Dev

18、elopment Kit Programming Reference describes how to develop your own native Info*Engine adapters using the Java programming language if the PTC adapter library does not contain an adapter that suits your needs. The Info*Engine Java Adapter Development Kit (including the documentation) is sold as a s

19、eparate product. See your sales representative for more information.The “Read This First” document, if one exists, provides additionalinformation about using the adapter that is not in this guide.If books are not installed on your system, see your system administrator.5Technical SupportContact PTC T

20、echnical Support through the PTC website, or by phone, email, or fax if you encounter problems using this product or the product documentation. The PTC eSupport portal provides the resources and tools to support your PTC Windchill implementation:/appserver/cs/portal/For complet

21、e details, see the PTC Customer Support Guide: /appserver/support/csguide/csguide.jspYou must have a Service Contract Number (SCN) before you can receive technical support. If you do not know your SCN, see “Preparing to contact TS” on the Processes tab of the PTC Customer Suppor

22、t Guide for information abouthow to locate it.Documentation for PTC ProductsYou can access PTC documentation using the following resources:PTC Windchill Help CenterThe PTC Windchill Help Center includes all PTC Windchill documentation. You can browse the entire documentation set, oruse the search ca

23、pability to perform a keyword search. To access the PTC Windchill Help Center, you can:Click any help iconin PTC WindchillSelect Help Windchill Help Center from the Quick Links menu at the top right of any PTC Windchill pageUse the following link to access all PTC help centers: https:/support.ptc.co

24、m/appserver/cs/help/help.jspReference Documents websiteThe Reference Documents website is a library of all PTC guides:/appserver/cs/doc/refdoc.jspA Service Contract Number (SCN) is required to access the PTC documentation from the Reference Documents website. If you do not know

25、your SCN, see “Preparing to contact TS” on the Processes tab of the PTC Customer Support Guide for information about how to locate it:/appserver/support/csguide/csguide.jspWhen you enter a keyword in the Search Our Knowledge field on the PTC eSupport portal, your search results

26、include both knowledge base articles andPDF guides.6SAPAdapter GuideCommentsPTC welcomes your suggestions and comments on its documentation. To submit your feedback, you can:Send an email to . To help us more quickly address your concern, include the name of the PTC product and i

27、ts release number with your comments. If your comments are about a specific help topic or book, include the title.Click the feedback iconin the PTC Windchill Help Center toolbar andcomplete the feedback form. The title of the help topic you wereviewing when you clicked the icon is automatically incl

28、uded with yourfeedback.About This Guide71Info*Engine ArchitectureIdentifying the Info*Engine Components10Identifying Basic Components11Interacting with Info*Engine11Managing the Execution of Info*Engine Tasks16Starting and Locating Info*Engine Components23Setting Up Connections Through Adapters25SAP

29、 Adapter Architecture.28In order to understand the operation of Info*Engine adapters, you must first understand how adapters work within the Info*Engine architecture. Thefollowing sections describe each component of the Info*Engine architecture and detailshow those components work in concert.9Identi

30、fying the Info*Engine ComponentsThe following components make up the Info*Engine architecture:Info*Engine ServletsInfo*Engine servlets provide an interface between the web server and Info*Engine.Info*Engine ServerThe Info*Engine server provides a mechanism for retrieving and manipulating the data th

31、at users or custom applications want to view or receive.Naming ServiceThe Naming Service is the software that supports the operation of Info*Engine components. In the Info*Engine Naming Service, you can identify the LDAP directory servers where entries for the network addresses of Info*Engine compon

32、ents and entries for configuration properties reside.Info*Engine Service Access Kit (SAK)The Info*Engine Service Access Kit (SAK) is an application program interface (API) that facilitates the development of Java applications, including JSP pages, that directly utilize the functions and features of

33、Info*Engine. For example, high-level Info*Engine components such as the IE servlet and the Info*Engine server use the SAK to invoke tasks and individual webjects.Native AdaptersThe native adapters provide a direct interface between Info*Engine and information systems.Non-Native AdaptersThe non-nativ

34、e adapters provide an indirect interface between Info*Engine and information systems. These adapters use a different protocol from the protocol used by Info*Engine and therefore cannot connect directly to Info*Engine.GatewaysGateways provide an interface between Info*Engine and non-native adapters.I

35、nfo*Engine SOAP ServletsThe Info*Engine SOAP servlets catch and process Info*Engine SOAP requests that are made over the web. SOAP (Simple Object Access Protocol) is a lightweight protocol that can be used by third-party applications. By using this protocol, third-party applications can send request

36、s to execute Info*Engine code and return the output that is generated.The remaining sections describe the relationships among the components.10SAPAdapter GuideIdentifying Basic ComponentsInfo*Engine components can be used in many different software and hardware configurations to meet your business r

37、equirements for accessing, managing, and presenting data from different information systems.Setting up your Info*Engine environment can be accomplished by:Establishing interactions with Info*Engine. Managing the execution of Info*Engine tasks. Starting and managing Info*Engine components.Managing co

38、nnections to the information systems where the data of interest resides.Interacting with Info*EngineInitiating an interaction with Info*Engine can be accomplished by using oneor more of the following:Java Server Pages (JSP)Custom external Java applicationsSimple Object Access Protocol (SOAP) web ser

39、vice Java Message Service (JMS)External applications processing XML over HTTP (or HTTPS)Info*Engine Architecture11The following diagram shows how Info*Engine components and othercustomer software components can interact to execute Info*Engine code:Info*Engine code consists of Java classes that are a

40、ccessed through the Info*Engine API. The API is available through the SAK and externalizes predefined functions called webjects and tasks. Webjects and tasks can beeasily instantiated and invoked as Java objects from a Java application or directlyfrom other Info*Engine tasks (stored as text files).T

41、he following sections provide more detail about how to use the Info*Engine components with your software.Java Server PagesThe installation process guides you through a procedure that deploys Info*Engine as a web application. Going through the installation process sets up your web server and its serv

42、let engine to identify Info*Engine requests and pass those requests on to Info*Engine components for processing. This sets up your Info*Engine environment so that the requests from web browsers to execute JSP and HTML pages are processed correctly.12SAPAdapter GuideThe following diagram shows the re

43、lationships among the componentsthat process web browser requests for JSP pages:This diagram shows the components that are used when a request specifies that Info*Engine execute a JSP page. By default, Info*Engine and web server configuration specifies that JSP pages are processed in the JSP engine

44、of the Tomcat servlet engine installed within the Windchill Method Server. The JSP engine creates an instance of the SAK, which is then used to execute the Info*Engine-specific code on the page. For example, if a user clicks a link oruses a URL in a browser window that serves as a JSP request for in

45、formation from Info*Engine, the JSP engine and the SAK work together to manage therequest.The SAK processes the request and, as needed, connects to specialized Info*Engine adapters that communicate with external applications such as Oracle databases, PDM systems, various legacy systems, and ERP syst

46、ems. After the requested information is obtained from the external applications, the process reverses itself and ultimately displays information in the users browser window.Web Browser Request ExampleThrough Info*Engine, the information from these two disparate systems can be combined and displayed

47、to the user at the same time. The first step is to author a JSP page that uses Info*Engine to request this information and then display the requested items in side-by-side frames within a browser window. Usually, this JSPInfo*Engine Architecture13page resides in the directory assigned to Info*Engine

48、 JSP pages. To display the page, the user includes the assigned Info*Engine application URL prefix in the URL. For example, assume the following:The web page is named bill_of_materials.jsp. The web server is named Wsvr1.The Info*Engine URL prefix that identifies where JSP pages resideisWindchill.To

49、initiate the request for the bill_of_materials JSP page, a user sends the following URL using HTTP:http:/Wsvr1/Windchill/bill_of_materials.jspBecause the URL contains the Windchill URL prefix, the web server passes the URL on to the JSP engine. The JSP engine then finds and processes the JSP page. I

50、n this example, the JSP page contains standard JSP and HTML tags that format the page to display the bill of material data in side-by-side frames.In addition to the standard tags, the JSP page contains custom Info*Engine tags that identify requests for the data that will fill out the bills of materi

51、al. Thecustom tags also provide the information that formats the data that is returned from the requests. When the JSP engine encounters the custom tags, it passes these tags off to the SAK for processing.When the SAK processes the custom tags on the JSP page, it performs the following tasks:Locates

52、 the information needed to access any requested applications (for example, the PDM or ERP system).Obtains any additional information that is required to retrieve, manipulate, and display the requested data.Identifies any authentication requirements (who can or cannot access the information requested

53、) if you set up custom tags to do so.To obtain the data, the SAK sends requests through the Info*Engine protocol to the appropriate Info*Engine adapters. After the appropriate PDM and ERP applications are located, the requested EBOM and MBOM data is retrieved and returned to the SAK. The SAK maintai

54、ns the data as two separate groups in an internal, virtual database (VDB).Using Info*Engine custom tags that the author has included in the JSP page, the data returned in these two groups is manipulated and formatted into standard HTML-encoded text. Then, the SAK returns the encoded text to the JSP

55、engine. The JSP engine passes the text back to the web server, which passes it back to the users browser to be displayed. As described earlier in this example, the display shows the data in the side-by-side frames that were set up for the EBOM and MBOM comparison originally requested by the user.14S

56、APAdapter GuideUsing a Custom External Java ApplicationBy coding a custom application in Java, you can have quick and easy accessto Info*Engine without the added complexity of a web server. By using the API defined in the SAK, you can execute Info*Engine webjects, tasks, and other Info*Engine code i

57、n the Java Virtual Machine (JVM) where the application resides.The following diagram shows the SAK and adapter classes being used in the application to access data in a remote database.Within a Java application, you also have the flexibility of executing Info*Engine tasks that are maintained outside

58、 of the application. An Info*Engine task consists of a set of webjects and surrounding code that supports the processing of the webjects. These tasks can then be processed either in the JVM of any Info*Engine server or in the JVM of the application.Info*Engine Architecture15The following diagram shows the Info*Engine components that are used whenan application executes