1 / 15

Remote Connectivity to XA R7/R9 Power-Link & Net-Link

Remote Connectivity to XA R7/R9 Power-Link & Net-Link. Denise Burns denise.burns@cistech.net (423)235-0673. Agenda. Summary of Remote Connectivity Options Review of Each Option Features Hardware/Software requirements Pros/Cons of Options Demo of each Option

shyla
Download Presentation

Remote Connectivity to XA R7/R9 Power-Link & Net-Link

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Remote Connectivity to XA R7/R9 Power-Link & Net-Link Denise Burns denise.burns@cistech.net (423)235-0673

  2. Agenda • Summaryof Remote Connectivity Options • Review of Each Option • Features • Hardware/Software requirements • Pros/Cons of Options • Demo of each Option 5. How We Can Help

  3. Summary of Options Power-Link XA Power-Link to Terminal Server/ Citrix XAX Net-Link

  4. Power-Link direct on WAN • Easiest option if you have enough bandwidth • Depends on number of users, applications, size of database, etc. • Client needs memory, 1 GB minimum • Total network performance is critical • Hubs, switches, cabling, etc. XA

  5. Power-Link direct on WAN Performance can be ‘tweaked’: • Remote fix server • Reduces startup time • Reduces effort to update clients • Utilize preferences to tailor user views and subsets • minimize subsets that bring up all records, i.e. IMHIST , items, orders XA PC Server

  6. Power-Link via Terminal Server XA • Remote user logs into Terminal Server • Terminal Server installed at iSeries location • Faster response time than running Power-Link client remotely • Terminal Services application included in Windows Server operating system • Must buy CAL for each user Terminal Server

  7. Power-Link via Terminal Server XA • Windows Terminal Server with user CAL’s: OS – Windows 2000, 2003 or 2008. Terminal Server CAL’s are approximately $80 each • Power-Link client on Terminal Server requires 100+ MB disk space (each env.) and minimum of 256 MB RAM Terminal Server

  8. Net-Link XA • Faster response time than running Power-Link client over same bandwidth remotely • Auxiliary Server Required: • OS – Windows 2000, 2003 or 2008 • Minimum hardware – P4, 2.8 GHz, 1 GB RAM (more recommended) • Allow 2 GB of memory for every 50 Net-Link users Auxiliary Server

  9. Pros/Cons – Power-Link • Power-Link via Terminal Server • Full functionality of Power-Link software • Additional server required for Terminal Services • Terminal Server CAL required for each user • Approximate cost $80/each If performance is not acceptable with Power-Link:

  10. Pros/Cons - Net-Link • Subset of Power-Link functionality • Probably not appropriate for Power User • Might be fine for limited/inquiry user • Utilizes less bandwidth with faster response time compared to Power-Link • Connection can be through VPN or external address can be set up in firewall for a connection from internet • No additional installation or software licensing required • Requires Auxiliary Server running a set of processes for every 50 Net-Link users

  11. Demonstration: Power-Link Power-Link with Terminal Server Net-Link

  12. How We Can Help • Power-Link via WAN • Install remote fix server • 1 day to implement if server OS is installed • Power-Link via Terminal Server • Install Terminal Server • 1 - 2 days to implement

  13. How We Can Help • Net-Link • Install Auxiliary Server • Assist network administrator with configuration of Net-Link for external access (across internet) • 1 day to implement • Other • Analyze network infrastructure and troubleshoot connectivity problems/performance issues

  14. Questions ?? Thank you!!

  15. Technical Information Denise Burns 423-235-0673 denise.burns@cistech.net Technical Information Ruth A. Pharr 704.814.0007 ruth.pharr@cistech.net Sales Information Ben McCormick 704.814.0016 ben.mccormick@cistech.net

More Related