DOCSLIB.ORG

JAVA COMPONENT DEVELOPMENT GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2017 Copyright Notice

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
JAVA COMPONENT DEVELOPMENT GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2017 Copyright Notice JAVA COMPONENT DEVELOPMENT GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2017 Copyright Notice ©2016 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with Pipeline Pilot." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected], or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Contents Chapter 1: Java Component Development Appendix D: Memory Management 30 Overview 1 Appendix E: Testing 31 Who Should Read this Guide 1 Requirements 1 Getting Started with Java Component Development 1 Java Component API 1 Component Interface 2 Supported Objects 2 Additional Information 2 Chapter 2: Creating Java Components 3 Application Package 3 Anatomy of a Java Component 3 Development Requirements 4 Creating a Java Component with Eclipse 4 Creating a Package 4 Creating a Java Project in Eclipse 5 Creating a Project Named "pilotcomponent" 5 Adding the External jar reference to the Build Path 9 Creating a Pilot Component Class 9 Using the Java API to Implement the Component Interface 10 Component Interface 11 Component Categories 11 Saving the Java Code 12 Activating the Package 12 Chapter 3: Testing a Java Component in Pipeline Pilot Client 14 Chapter 4: Adding New Java Components to a Package 16 Saving Components in Package Destinations 16 Chapter 5: Distributing the Package 18 Chapter 6: Debugging a Java Component 19 Writing Additional Properties to the Output 19 Printing Debug Messages 21 Debugging with Eclipse IDE 22 Notes on Debugging 24 Appendices 26 Appendix A: Java VM Environment 26 Appendix B: Using JNI within a Java Component 26 Appendix C: Hash Table Values 26 Creation from a Java Map 27 Values as Java Maps 28 Comment on null values 30 Chapter 1: Java Component Development Overview The Pipeline Pilot Integration collection includes tools for developing components in the Java programming language for use with protocols. Java is a powerful environment for experienced programmers who need to develop and deliver high-performance capabilities. Java is known for its speed and ability to integrate the capabilities of a pre-existing Java library. If speed is not an issue, it may be easier to use a scripting language such as Perl, Python, or VB. Who Should Read this Guide This guide provides information about how to use the Java component application programming interface (API) to access and modify data objects for developing your own components. It offers the necessary architectural background and technical instructions for creating, testing, and deploying your customized Java components. Requirements To develop components in Java, you need the following: Experience writing code in Java A Java-integrated development environment (IDE), such as Eclipse 3.1 You should also have a basic understanding of how to use Pipeline Pilot Client to design and run protocols Note: This document assumes you are familiar with the Protocol Development Quick Start guide, which explains Component Lifetime Management. Getting Started with Java Component Development The tools available for developing components in Java include: Java-based components, such as Java (on Server) Java API and accompanying API documentation API examples that demonstrate how to design Java components that access the Pipeline Pilot data model to carry out a variety of tasks. A set of template Java Classes to use as a starting point for creating different types of Java components that call the API, such as calculators, manipulators, filters, readers, and writers. This guide includes instructions that walk you through the steps of creating a new component using the Java API, based on the Java (on Server) component that acts as a common "empty vessel" for all Java components. Java Component API The Java Component API provides a convenient way to access and modify the data structures, including the data records that flow through the components, the various parameter settings, and the global properties of the enclosing protocol. Java Component Development Overview | Page 1 The API is implemented in an object-oriented fashion that reflects the natural syntax and features of the Java programming language. For the API definition, refer to the published Javadocs. Component Interface The Java component interface is com.scitegic.pilot.Component. Every Java component implements the following methods, which are detailed in this guide: Component.onInitialize: Executed once before processing the first data record. Component.onProcess: Executed for each data record passed as input or generated by the component. Component.onFinalize: Executed after processing the last data record. The support of this interface is what allows the Java component to plug and play in protocol. Supported Objects The objects implemented by the Java API include: com.scitegic.pilot.DataRecord: The data upon which the component operates to implement its function. com.scitegic.pilot.Node: An element of the data record and global data hierarchies. com.scitegic.pilot.PropertyCollection: An ordered set of name/value pairs used to hold the properties assigned to each node and to represent parameter settings. com.scitegic.pilot.Property: One of the name/value pairs in a property collection. com.scitegic.pilot.Value: A generic value object used to define name/value pairs in a property collection. com.scitegic.pilot.Context: Passed to the Component interface methods above, to allow access to component parameters and global properties. Additional Information For more information about the Pipeline Pilot Integration collection and other BIOVIA software products, visit https://community.3dsbiovia.com. Page 2 | Pipeline Pilot • Java Component Development Guide Chapter 2: Creating Java Components The following topics are covered: Application Package Anatomy of a Java Component Development Requirements Creating a Java Component with Eclipse Activating the Package Application Package To deploy and run a Java component, you need to work within a named package. A package is a directory structure that holds all files required to deploy an application—binaries, component XML, example protocols, example data files, and documentation. All components in Pipeline Pilot are deployed in packages, representing licensed modules. The package approach is particularly important for components that include a separately compiled binary content, such as Java components. IMPORTANT! We recommend that you become familiar with the packaging concept described in the Application Packaging Guide. The "package.conf" file at the top of the package directory structure provides details about how everything is organized in this package and other configuration information. To make a Java component accessible to Pipeline Pilot, define CLASSPATH within java directive in "package.conf", pointing to the location of your classes. <java> CLASSPATH$(package)/…/classes </java> or .jar <java> CLASSPATH$(package)/…/jars/your_component.jar </java> Anatomy of a Java Component When completed, a Java component consists of two parts that reside within a package file structure: A Java class that implements the interface com.scitegic.pilot.Component. The jar file (included in the Integration collection) required to build such classes is "<install_ root>/apps/scitegic/integration/bin/lang/java/jars/pilot.jar" An instance of the Java (on Server) component with its JavaClass and Use Package parameters set to refer to the appropriate class and package. This is the XML definition of the interface that is exposed to a protocol designer in the Pipeline Pilot Client. It defines the component parameters, default parameter values, the component icon, and configuration of input and output ports. Creating Java Components | Page 3 Development Requirements To implement Java components, be sure you have the following resources available: Develop the Java components on a server and write the compiled class files on the same server for testing. We recommend using a dedicated server for developing and debugging Java components. Creating a Java Component with Eclipse This example provides step-by-step instructions on how to create a Java component using Eclipse 3.1 as the Java development environment. IMPORTANT! Before you start, ensure that Eclipse is configured to use Java 5.0 features. From Eclipse, select Window > Preferences > Java > Compiler. Set the Compiler compliance level to "5.0", and enable the flag for Use default compliance settings. To work with this example, use a command window on your server. The example includes the following steps: Creating a package Creating a Java project in Eclipse that implements the Pipeline Pilot component
Load more

Recommended publications
  • 3 Workflow Systems
    Large Scale Data Handling in Biology Workflow Systems 3 Workflow Systems Within the last few years a large number of tools and softwares dealing with different computational problems related to HCS have been developed. Incorporating third party or new tools into existing frameworks needs a flexible, modular and customizable workflow framework. Workflow (Pipeline) systems could become crucial for enabling HCS researchers doing large scale experiments to deal with this data explosion. The workflow is termed abstract in that it is not yet fully functional but the actual components are in place and in the requisite order. In general, workflow systems concentrate on the creation of abstract process workflows to which data can be applied when the design process is complete. In contrast, workflow systems in the life sciences domain are often based on a data-flow model, due to the data-centric and data-driven nature of many scientific analyses. A comprehensive understanding of biological phenomena can be achieved only through the integration of all available biological information and different data analysis tools and applications. In general, an ideal workflow system in HCS can integrate nearly all standard tools and software. For example, for an HCS using small molecules, the workflow system must be able to integrate different image processing software and data mining toolkits with flexibility. The possibility that any single software covers all possible domains and data models is nearly zero. No one vendor or source can provide all the tools needed by HCS informatics. So it is suggested that one uses specialized tools from specialized sources. Also not all softwares components can be integrated with all workflow systems.
    [Show full text]
  • BIOVIA Pipeline Pilot System Requirements
    SYSTEM REQUIREMENTS PIPELINE PILOT 2020 Copyright Notice ©2019 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3DVIA, 3DSWYM, BIOVIA, NETVIBES, IFWE and 3DEXCITE, are commercial trademarks or registered trademarks of Dassault Systèmes, a French "société européenne" (Versailles Commercial Register # B 322 306 440), or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained by using Dassault Systèmes software, acknowledge the source in an appropriate format. For example: "Computational results were obtained by using Dassault Systèmes BIOVIA software programs. Pipeline Pilot Server was used to perform the calculations and to generate the graphical results." Dassault Systèmes may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to Dassault Systèmes Customer Support, either by visiting https://www.3ds.com/support/ and clicking Call us or Submit a request, or by writing to: Dassault Systèmes Customer Support 10, Rue Marcel Dassault 78140 Vélizy-Villacoublay FRANCE Contents About This Document 1 Definitions 1 Additional Information 1 Dassault Systèmes Support Resources 1 Pipeline Pilot Server Requirements 2 Minimum Hardware
    [Show full text]
  • Integration Collection for Pipeline Pilot
    QUICK START GUIDE PROTOCOL DEVELOPMENT INTEGRATION COLLECTION 2017 Copyright Notice ©2016 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with Pipeline Pilot." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected], or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Contents Chapter 1: Introduction 1 Run Program 17 Architectural Overview 1 Run Program on Remote Host 18 Extending Functionality 2 SOAP 18 Application Integration Components 3 Chapter 4: Language-Based Components 19 Command-line Integration 3 Perl 19 Run Program Components 3 Java 20 FTP 3 .NET 20 SSH 3 Windows Script Host Components 20 SCP 4 Python 21 Telnet 4 VBScript 21 Language-based Integration 4 PilotScript 21 Java Component Development 4 About the PilotScript Language 21 .NET Component Development 4 PilotScript vs.
    [Show full text]
  • Accelrys Enterprise Platform
    ADMIN PORTAL GUIDE PIPELINE PILOT 2017 Copyright Notice ©2016 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with Pipeline Pilot." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected], or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Contents Chapter 1: Introduction 1 Diagnostic Tools for Apache 16 BIOVIA Pipeline Pilot Server Overview 1 Admin Portal User Assistance 16 Supported Operating Systems 1 Getting Help in the Admin Portal 16 Client Software 1 Tooltips 16 Developer Tools 1 Expanding Help 17 Enterprise Architecture 1 Pipeline Pilot Help Center 18 Protocol Database Sharing
    [Show full text]
  • DEVELOPER GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 Copyright Notice
    DEVELOPER GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 Copyright Notice ©2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with Pipeline Pilot." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected], or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Contents Chapter 1: Introduction 1 Property List Interface 19 Windows Script Host (WSH) 1 Interface Methods for Data, Globals and General Requirements 1 Parameters Objects 19 Additional Information 2 Chapter 8: Handling Errors 23 Chapter 2: Scripting Components 3 Reporting Errors in VBScript 23 VBScript Components 3 Reporting
    [Show full text]
  • Multiple Usage of KNIME in a Screening Laboratory Environment
    Multiple Usage of KNIME in a Screening Laboratory Environment KNIME UGM Zürich, 02.02.2012 Marc Bickle HT-TDS, MPI-CBG Outline • Presentation of TDS • Our problem: large complex datasets • KNIME as data mining tool for screening (Community nodes) • HCS tools (Community nodes) • R, python, Matlab, Groovy integration • Some examples of other usage of KNIME The High Throughput Technology Development Studio (HT-TDS) Mission: provide cell-based screening services Automated microscopy and automated image analysis • High spatio-temporal resolution on a cell-by-cell basis • Quantitative measurement of many cellular parameters (intensity, sub cellular localization) allowing finely resolved phenotypic classification • System biology readouts of chemogenomic screens (genome-wide RNAi screens + chemical screens) • Clustering of RNAi and chemical phenotypes for mode-of-action identification (170.000 cpds, GW libraries) shape of cells number of nuclei intensity Automated Confocal Microscopy Profiling/clustering • high resolution • advanced statistics • high throughput • identify target of compounds distribution/distance Automated Image Analysis sub cellular localization • multiple parameters • high definition of phenotypes Identifying MOA By Integrating Chemical And Genetic Screens Compound Screen RNAi Screen 6.0 CHML all oligos run 5 6.0 CHML all oligos run 5 4.0 4.0 2.0 2.0 0.0 0.0 -2.0 -2.0 -4.0 0.0 5.0 10 15 20 25 30 35 40 -4.0 0.0 5.0 10 15 20 25 30 35 40 What genes influence the same parameters as the compounds ? Devise assays to test predictions upon pathways Image Screen Dataflow 1-10 Mio Images (tif) 2-10TB Image Analysis 1-10 x 104 wells 1-10x 106 fields 1-10 x 108 cells 1-10 x 1010 objects CSV files/database 2-100GB 1-10 Mio Images (png) Data Mining 1-50 plots (png/svg) 7 (2010)7 1-10 result files - 1 doi:10.1038/nature08779 C Collinet al.000, Natureet (CSV/xls/pdf) 1-10MB Available Software Solutions • Few software are able to deal with n-dimensional data structures of several GB size 1.
    [Show full text]
  • List of Applications Updated in ARL #2581
    List of Applications Updated in ARL #2581 Application Name Publisher .NET Core Runtime 3.0 Preview Microsoft .NET Core Toolset 3.1 Preview Microsoft .NET Framework 4.5 Microsoft .NET Framework 4.6 Microsoft .NET Framework Developer Pack 4.7 Microsoft .NET Framework Multi-Targeting Pack for Windows Store Apps 4.5 RC Microsoft .NET Framework SDK 4.8 Microsoft _connect.BRAIN 4.8 Bizerba 2200 TapeStation Software 3.1 Agilent Technologies 2200 TapeStation Software 3.2 Agilent Technologies 24x7 Automation Suite 3.6 SoftTree Technologies 3500 Rack Configuration Software 6.0 Bently Nevada 365 16.0 Microsoft 3D Sprint 2.10 3D Systems 3D Sprint 2.11 3D Systems 3D Sprint 2.12 3D Systems 3D Viewer Microsoft 3PAR Host Explorer VMware 4.0 HP 4059 Extended Edition Attendant Console 2.1 ALE International 4uKey 1.4 Tenorshare 4uKey 1.6 Tenorshare 4uKey 2.2 Tenorshare 50 Accounts 21.0 Sage Group 50 Accounts 25.1 Sage Group 793 Controller Software 5.8 MTS Systems 793 Controller Software 5.9 MTS Systems 793 Controller Software 6.1 MTS Systems 7-Zip 19.00 Igor Pavlov ABAQUS 2018 Student Dassault Systemes ABAQUS 2019 Student Dassault Systemes Abstract 73.0 Elastic Projects ABU Service 14.10 Teradata Access Client 3.5 Barracuda Networks Access Client 3.7 Barracuda Networks Access Client 4.1 Barracuda Networks Access Module for Azure 15.1 Teradata Access Security Gateway (ASG) Soft Key Avaya AccuNest 10.3 Gerber Technology AccuNest 11.0 Gerber Technology ACDSee 2.3 Free ACD Systems ACDSee 2.4 Free ACD Systems ACDSee Photo Studio 2019 Professional ACD Systems
    [Show full text]
  • List of New Applications Added in ARL #2543
    List of New Applications Added in ARL #2543 Application Name Publisher 1-4a Rename 1.56 1-4a.com SyncBackFree 3.2 2BrightSparks SyncBackFree 7.6 2BrightSparks SyncBackFree 9.3 2BrightSparks IP Eye 1.4 2N Technologies 3DxPair 2.0 3Dconnexion 3DxSoftware 3.18 SpacePilot Pro 3Dconnexion 3DxCollage 3Dconnexion 3DxNumpad 3Dconnexion 3DxSoftware 3.17 3Dconnexion Picture Viewer 1.5 3Dconnexion 3DxSoftware 3.16 3Dconnexion 3DxPair 2.1 3Dconnexion 3DxTrainer 3.2 3Dconnexion Core Grouping Software Client 2017.0 3M Core Grouping Software Client 2017.1 3M 360 Encompass System Update Tool 2.1 3M EARfit 3M Core Grouping Software 2017.1 3M 3M Client 7.3 3M Core Grouping Software Client 2018.1 3M Core Grouping Software 2017.3 3M Core Grouping Software 2018.1 3M Core Grouping Software Client 2018.0 3M 360 Encompass System WebCvConfig 30.2 3M Core Grouping Software 2018.0 3M CS Encryption Utility 2.0 3M Core Grouping Software 2017.0 3M Core Grouping Software 2017.2 3M 3M Client 7.2 3M 360 Encompass System WebCvConfig 18.2 3M 360 Encompass System WebCvConfig 24.1 3M Core Grouping Software Client 2018.2 3M WinAppLink 1.0 3M 360 Encompass System WebCvConfig 22.2 3M Core Grouping Software 2018.2 3M Core Grouping Software Client 2017.2 3M Core Grouping Software Client 2017.3 3M 360 Encompass System Application Services 3.3 3M 360 Encompass System 3M 3D Lift Plan A1A Software AAONECat32 4.0 AAON StriePlan ABB MineScape SDK 5.12 ABB MineScape Help 5.12 ABB HostsMan 3.2 abelhadigital PC Gateway ABM Sensor Technology HAZUS ABS Consulting Custodium Plugin 1.1 Acepta
    [Show full text]
  • Workflow and Pipelining in Cheminformatics
    Integration, Analysis and Collaboration. An Update on Workflow and Pipelining in Cheminformatics The workflow paradigm is a generic mechanism to integrate different data resources, software applications and algorithms, Web services and shared expertise. Such technologies allow a form of integration and data analysis that is not limited by the restrictive tables of a conventional database system. They enable scientists to construct their own research data processing networks (sometimes called “protocols”) for scientific analytics and decision making by connecting various information resources and software applications together in an intuitive manner, without any programming. Therefore, software from a variety of vendors can be assembled into something that is the ideal workflow for the end user. These are, purportedly, easy-to-use systems for controlling the flow and analysis of data. In practice, certainly in chemical analyses, they are not generally used by novices: best use of the system can be made by allowing a computational chemist to set up the steps in a protocol then “publish” it for use by other scientists on the Web. Until recently, in the cheminformatics field, only two solutions were in common use for capturing and executing such multi-step procedures, processing entire data sets in real time through “pipelines” or “workflows”. The two technologies, both of them commercial solutions, are from InforSense,1 which uses a workflow paradigm in its InforSense platform, and SciTegic2 (now part of Accelrys) which uses data pipelining in Pipeline Pilot. New entrants to the market now open up many more options. Pipeline Pilot In Pipeline Pilot, users can graphically compose protocols, using hundreds of different configurable components for operations such as data retrieval, manipulation, computational filtering, and display.
    [Show full text]
  • Admin Portal Guide Pipeline Pilot 2016
    ADMIN PORTAL GUIDE PIPELINE PILOT 2016 Copyright Notice ©2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with Pipeline Pilot." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected], or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Contents Chapter 1: Introduction 1 Diagnostic Tools for Apache 15 BIOVIA Pipeline Pilot Server Overview 1 Diagnostic Tools 15 Supported Operating Systems 1 Admin Portal User Assistance 16 Client Software 1 Getting Help in the Admin Portal 16 Developer Tools 1 Tooltips 16 Enterprise Architecture 1 Expanding Help 17 Protocol Database Sharing and Data
    [Show full text]
  • Deployment Guide Pipeline Pilot Server 2016
    DEPLOYMENT GUIDE PIPELINE PILOT SERVER 2016 Copyright Notice ©2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with Discovery Studio Collection." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected] or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Page 2 | Pipeline Pilot 2016 Contents About This Document Tuning Server Settings................................................ 31 Getting Help ................................................................. 4 Admin Portal job settings ........................................ 31 Job pool configuration ............................................
    [Show full text]
  • WINDOWS SCRIPTING INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2017 Copyright Notice
    WINDOWS SCRIPTING INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2017 Copyright Notice ©2016 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with Pipeline Pilot." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected], or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Contents Chapter 1: Introduction 1 Property List Interface 19 Windows Script Host (WSH) 1 Interface Methods for Data, Globals and General Requirements 1 Parameters Objects 19 Additional Information 2 Chapter 8: Handling Errors 23 Chapter 2: Scripting Components 3 Reporting Errors in VBScript 23 VBScript Components
    [Show full text]