Remote Development Using Spod

Remote Development Using Spod

Natural for Windows Remote Development Using SPoD Version 6.3.8 for Windows February 2010 This document applies to Natural Version 6.3.8 for Windows. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Copyright © 1992-2010 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America, and/or their licensors. The name Software AG, webMethods and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc. and/or their licensors. Other company and product names mentioned herein may be trademarks of their respective owners. Use of this software is subject to adherence to Software AG's licensing conditions and terms. These terms are part of the product doc- umentation, located at http://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s). This software may include portions of third-party products. For third-party copyright notices and license terms, please refer to "License Texts, Copyright Notices and Disclaimers of Third-Party Products". This document is part of the product documentation, located at http://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s). Table of Contents 1 Remote Development Using SPoD .................................................................................. 1 2 Accessing a Remote Development Environment ............................................................ 3 Mapping a Development Server ................................................................................ 4 Connecting to a Mapped Development Server .......................................................... 6 Disconnecting a Mapped Development Server ......................................................... 7 Unmapping a Development Server ........................................................................... 7 3 Object Locking ................................................................................................................. 9 Object Locking Concept ........................................................................................... 10 Locking and Unlocking of Local and Remote Objects ............................................. 11 Unlocking Objects Manually .................................................................................... 11 Natural Development Server Restrictions ............................................................... 13 4 Natural Web I/O Interface Client .................................................................................. 15 About the Natural Web I/O Interface Client ............................................................ 16 Prerequisites for the Natural Development Server .................................................. 17 Working with the Natural Web I/O Interface Client ................................................ 17 Modifying Color and Field Attributes ..................................................................... 18 5 Terminal Emulation ....................................................................................................... 23 About Terminal Emulation ...................................................................................... 24 Prerequisites for the Natural Development Server .................................................. 25 Working in a Terminal Emulation Screen ................................................................ 25 Displaying a Keypad ................................................................................................ 26 Transferring Data Using the Clipboard ................................................................... 26 Modifying the Font .................................................................................................. 29 Modifying the Color Scheme ................................................................................... 30 Printing the Contents of a Terminal Emulation Screen ........................................... 35 Terminal Emulation Keys ......................................................................................... 36 Using Non-Latin Character Sets .............................................................................. 37 Translation Tables ..................................................................................................... 37 6 Managing Applications ................................................................................................. 43 About the Application Workspace ........................................................................... 44 Connecting to an Application Server ....................................................................... 45 Creating a New Application .................................................................................... 46 Linking Objects and Applications ............................................................................ 50 Mapping and Unmapping Applications .................................................................. 55 Connecting and Disconnecting Base Applications .................................................. 57 Displaying/Changing the Properties of the Application Server .............................. 58 Displaying/Changing the Properties of an Application .......................................... 59 Copying, Renaming and Deleting Applications ...................................................... 61 Cataloging Objects in the Application Workspace .................................................. 62 7 Using the Application Wizard ....................................................................................... 63 iii iv 1 Remote Development Using SPoD This documentation applies to the client side of Natural Single Point of Development (SPoD). It is complemental to the Using Natural Studio documentation in that it provides information on several features of Natural Studio which apply only when you are working in a remote development environment using SPoD. Note: The Natural Studio plug-ins which can only be used in a remote development envir- onment (such as Object Description which can be used with Predict) are not documented in this Natural for Windows documentation. See the Single Point of Development document- ation, which is provided separately, for detailed descriptions of these plug-ins. This documentation is organized under the following headings: Accessing a Remote How to use the library workspace to map to remote server Development Environment environments. Object Locking Describes the locking mechanism that is available in a remote development environment. Natural Web I/O Interface Client How to use the Natural Web I/O Interface client which appears in a remote development environment to display non-GUI information which contains Unicode characters. Terminal Emulation How to use the terminal emulation window which appears in a remote development environment to display non-GUI information. The terminal emulation window is not Unicode-enabled. Managing Applications How to use the application workspace which is used to administer all Natural applications in the remote environment(s) in a hierarchical manner as a tree view. Using the Application Wizard How to invoke the Application Wizard. 1 Remote Development Using SPoD Using the SPoD utility protocol, it is possible to extend your Natural development environment with user-written tools. See the Single Point of Development documentation, which is provided separately, for detailed information. SPoD-specific limitations and considerations are included in the Natural Development Server documentation for the corresponding platform. This documentation is also provided separately. 2 Remote Development Using SPoD 2 Accessing a Remote Development Environment ■ Mapping a Development Server ........................................................................................................... 4 ■ Connecting to a Mapped Development Server ........................................................................................ 6 ■ Disconnecting a Mapped Development Server ........................................................................................ 7 ■ Unmapping a Development Server ....................................................................................................... 7 3 Accessing a Remote Development Environment Natural Studio's library workspace can also be used to administer the Natural system files of a remote server environment. Mapping a Development Server To perform remote development, you have to activate a remote Natural environment. You do this by connecting to the appropriate development server. Each development server provides all remote services (such as access or update) for a specific FUSER (Natural system file for user programs). If you want to use a development server for the first time, you have to map it as described below. Once you have mapped a development server, a node for this development server session is automatically shown in the library workspace. It is possible to map the same development server more than once, for example, if you want to have development-server sessions with different session parameters. To switch to another session, you simply select the corresponding node in your library workspace. If you do not know the name and port number for your development server, ask your administrator. To map a development server

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    68 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us