Difference between revisions of "BPCS Infrastructure"

From MidrangeWiki
Jump to: navigation, search
(What is Client Server Infrastructure ?)
(What is Client / Server ?)
Line 102: Line 102:
 
* It is NOT some specific software.   
 
* It is NOT some specific software.   
 
* It is NOT some specific hardware.   
 
* It is NOT some specific hardware.   
- * It is NOT a solution for all applications.   
+
* It is NOT a solution for all applications.   
- == Sane Planning ==   
+
== Sane Planning ==   
- * Project Organization, as with any other conversion   
+
* Project Organization, as with any other conversion   
- ** Define Objectives, Schedule (a moving target)   
+
** Define Objectives, Schedule (a moving target)   
- ** Management Approval, Budget Commitment   
+
** Management Approval, Budget Commitment   
- ** Team Membership   
+
** Team Membership   
- *** Key IT leadership   
+
*** Key IT leadership   
- *** Application Design management   
+
*** Application Design management   
- *** IT Operations Support management   
+
*** IT Operations Support management   
- *** Consultants   
+
*** Consultants   
- ** Set hierarchy ... team leader   
+
** Set hierarchy ... team leader   
- * Assess exisitng infrastructure inventory   
+
* Assess exisitng infrastructure inventory   
- * Four layers     
+
* Four layers     
- ** Logical Architecture   
+
** Logical Architecture   
- *** What MIS does to support the business   
+
*** What MIS does to support the business   
- *** What the users need   
+
*** What the users need   
- *** Business vision   
+
*** Business vision   
- ** Physical Architecture   
+
** Physical Architecture   
- *** Site specific   
+
*** Site specific   
- *** technologies that define or limit what we can do   
+
*** technologies that define or limit what we can do   
- ** Enabling Technologies   
+
** Enabling Technologies   
- *** Operating Systems   
+
*** Operating Systems   
- *** Middleware   
+
*** Middleware   
- *** Systems and Network management   
+
*** Systems and Network management   
- *** Security   
+
*** Security   
- *** Configuration   
+
*** Configuration   
- *** Trouble-shooting   
+
*** Trouble-shooting   
- *** Performance   
+
*** Performance   
- ** Support   
+
** Support   
- *** What it takes to meet regulatory constraints   
+
*** What it takes to meet regulatory constraints   
- *** Planning   
+
*** Planning   
- *** Development   
+
*** Development   
- *** Different kinds of support   
+
*** Different kinds of support   
- **** Hardware   
+
**** Hardware   
- **** Network   
+
**** Network   
- **** Application   
+
**** Application   
- **** Training new users   
+
**** Training new users   
- **** Skill sets ... same person   
+
**** Skill sets ... same person   
- ***** AS/400 and PC and telecom   
+
***** AS/400 and PC and telecom   
- **** Documenting   
+
**** Documenting   
- * Design   
+
* Design   
- ** Diagrams that make sense to everyone   
+
** Diagrams that make sense to everyone   
- ** Testing   
+
** Testing   
 
* Implementation
 
* Implementation

Revision as of 20:09, 26 June 2005

RPG vs. RPG from AS/SET

Once upon a time 100% of BPCS was written by human beings, then AS/SET was invented to support BPCS able to run on other platforms than the 400, such as UNIX. Over time, less and less of BPCS was written in 400 programming languages, so that access to AS/SET became more critical. In later versions, SSA does not release the RPG CLP etc. source code, whether it comes from human programming, or is generated thru AS/SET.

As we move to later versions of BPCS, we have to decide whether we need what source code, and also get AS/SET.

Green Screen vs. Client Server

BPCS can run in a variety of different Infrastructures:

  • 100% Twinax Green Screen
  • mixture of Twinax and access thru PC GUI such as Client Access
  • 100% Client Access used to access the Green Screen software
  • A version of BPCS in which some or all of the programs have been re-written to function such that some of the application software runs on the PC and some runs on the 400.
  • Full Client Server is the name for version of BPCS in which 100% of it is that way.
  • Mixed Mode is the name for version of BPCS in which we support Twinax Green Screen and JOBQ and can access BPCS via PC GUI that emulates the Green Screen
  • We can also have a mixture in which some of the software is running Mixed Mode and some is running Client Server.
  • Whatever mixture is on a particular 400, this imposes Infrastructure demands on the 400, and there is a large challenge involved in converting from one reality to another.

When contemplating switching from one mixture to another, which typically orrurs in a conversion to a more advanced version of BPCS, it is important to understand the significance of the infrastructure differences.

What is Client Server Infrastructure ?

This is a set of principles, guidelines, and rules used by an organization to direct the process of acquiring, building, modifying and interfacing with IT resources throughout the enterprise.

Resources needed
  • Cable Systems for interconnecting equipment
  • Equipment
  • How much disk space and other 400 resources we need
    • BPCS sizing questionairre
  • How connect PCs to 400
    • spend $150 per PC and PC printer to connect to twinax and know next to nothing when something goes wrong or spend much more $ on a better quality interface
    • network PCs to a PC-based server then network the PC server to the 400
    • mix and match IBM and 3rd party solutions
  • Software
  • Communications protocols
  • Remote site support
  • How we connect thru ma bell
  • Application development
  • Methodology
  • Data base systems
  • Shared pool of documentation
  • Security
  • IT Organizational structure
  • IT professional skills
    • GUI software updates
    • Relational data base concepts
    • SQL
    • Network management
    • Integrate new technologies with base software applications such as BPCS
      • e-mail
      • fax
      • EDI
      • bar coding & data collection
      • Internet access
        • re-think security where before it was Ok to assume 99% users trustworthy, now we have a world of hackers and malware out there
  • Help Desk services

What ERP Version is best?

BPCS Choices

Decisions decisions

  • Mixed Mode or full Client Server?
    • Fat and Thin Clients
    • Mixed Mode
      • Client Server for which applications
        • Accounting
        • Customer Service
        • Supply Chain
      • Green Screen for everything else
      • Need Netsoft Router
    • Full Client Server
      • Fat Client for which applications
        • Accounting
        • Customer Service
        • Supply Chain
      • Thin Client for everything else
      • Need TCP/IP
    • UserVision has some Windows minimum requirements
      • UserVision is a BPCS GUI Business Intelligence Application
  • Client setup
    • 16 bit or 32 bit
    • What versions of Microsoft Windows
    • Are SSA minimums appropriate?
  • Network
    • Ethernet or Token Ring if Client Server
    • Twinax r IBM Cabling System for Mixed Mode
    • Examine Network Segmentation Growth Constraints
    • Network Management
      • Wireless opens another door into Security hassles
  • Network OS - Windows NT follow-on or Netware?
  • Network Server - BPCS FSIOP or separate server?
  • Different 3rd party support vendors are more attuned to different mixtures of solutions
    • If you go with one mixture, and use a tech support place whose expertise is in a different mixture, expect problems down the road

What is Client / Server ?

Client / Server computing is the splitting of an application into tasks that are performed on separate computers, one of which is a programmable workstation.

  • Client is the computing resource that is USING some resource provided by a Server.
  • Server is the computing resource that is PROVIDING some resource to Clients.
  • There can be a linkage or hierarchy of multiple Clients of Servers, in which the Clients are in turn Servers to other Clients.

Client/Server Computing is NOT

  • It is NOT some specific software.
  • It is NOT some specific hardware.
  • It is NOT a solution for all applications.

Sane Planning

  • Project Organization, as with any other conversion
    • Define Objectives, Schedule (a moving target)
    • Management Approval, Budget Commitment
    • Team Membership
      • Key IT leadership
      • Application Design management
      • IT Operations Support management
      • Consultants
    • Set hierarchy ... team leader
  • Assess exisitng infrastructure inventory
  • Four layers
    • Logical Architecture
      • What MIS does to support the business
      • What the users need
      • Business vision
    • Physical Architecture
      • Site specific
      • technologies that define or limit what we can do
    • Enabling Technologies
      • Operating Systems
      • Middleware
      • Systems and Network management
      • Security
      • Configuration
      • Trouble-shooting
      • Performance
    • Support
      • What it takes to meet regulatory constraints
      • Planning
      • Development
      • Different kinds of support
        • Hardware
        • Network
        • Application
        • Training new users
        • Skill sets ... same person
          • AS/400 and PC and telecom
        • Documenting
  • Design
    • Diagrams that make sense to everyone
    • Testing
  • Implementation