Lansa Development V12

1,611 views

Published on

How to configure your LANSA Development environment for your enterprise.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,611
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Lansa Development V12

  1. 1. LANSA Administration<br />Administration of LANSA Development<br />Development Environments<br />Task Tracking<br />Repository Synchronization <br />Development Flow with Task Tracking<br />Administration of LANSA Deployments<br />IBM iOnly<br />Windows Clients w/ IBM iServer<br />Windows Clients w/ Windows Server<br />Windows Clients w/ Unix Server<br />1<br />
  2. 2. Administration of LANSA Development<br />Development Environments<br />DEV – Development Environment<br />Use Task Oriented Task Tracking<br />Use Repository Synchronization<br />All development is done in this Environment<br />TST – Testing Environment<br />Updated via exports by task from DEV<br />No changes allowed in this environment<br />Compiles for “Level Checks” on IBM i<br />2<br />
  3. 3. Administration of LANSA Development<br />Development Environments<br />RLS – Staged for Release (optional)<br />Updated via exports by task from DEV<br />No Changes allowed in this environment<br />Compiles for “Level Checks” on IBM i<br />PRD – Production<br />Update via exports by task from DEV<br />No Changes allowed except in emergency<br />Compiles for “Level Checks” on IBM i<br />3<br />
  4. 4. Administration for Development<br />All development with detailed task tracking<br />Environment for QA after programmer tests<br />Optional, staging for deployment<br />Production or current release for ISVs<br />4<br />Development<br />Test<br />Ready to Deploy<br />Production<br />
  5. 5. Administration of LANSA Development<br />Development Environments<br />Each partition should be separate LANSA installation<br />Allow for change & testing of LANSA system wide options or objects<br />Insures that all necessary objects are sent from one system to another<br />Allow for LANSA upgrades to be tested prior to deployment to development or production<br />5<br />
  6. 6. Administration of LANSA Development<br />Development Environments<br />IBM i Master System<br />Windows Client Slave Systems<br />Database on Each Client<br />Development utilizes Check-in & Check out <br />Repository Synchronization keeps Windows Clients in sync<br />Windows Server Slave System<br />Development utilizes Check-in & Check out <br />No Repository Synchronization Required<br />Use LANSA Network Clients for local developers<br />Requires license on each Client PC or server license<br />Citrix/Terminal Server Clients for remote developers<br />Requires license on Windows Server or server license<br />6<br />
  7. 7. Administration of LANSA Development<br />Development Environments<br />Windows Master System<br />Network Client Installation for local developers<br />Requires license on each Client PC or Server license<br />Citrix/Terminal Server Clients for remote developers<br />Requires license on Windows Server or server license<br />Utilize “deliver to” capability to move software to IBM i or Linux<br />Utilize deployment tool to move software to Windows Servers<br /> Stand-alone Windows Master<br />Provides for single user local development on Client PC<br />Requires license on theClientPC or Server license<br />Utilize “deliver to” capability to move software to IBM i or Linux<br />Utilize deployment tool to move software to Windows Servers<br />7<br />
  8. 8. Administration of LANSA Development<br />Methods of Task Tracking<br />Reminder Based Task Tracking<br />Product / Developer / Minimum<br />User must manually manage changes<br />Task-oriented Task Tracking<br />Provides control over development<br />Provides control over developers<br />System manages changes<br />Instills discipline in development process<br />8<br />
  9. 9. Administration of LANSA Development<br />Task Oriented Task Tracking<br />Each new feature you are adding should be tracked separately –- WHY?<br />Highly recommend a task for the database changes separate from the new feature –- WHY? <br />Setup of task(s) could be done with the specification of the requirement<br />Manage task conflicts manually as exceptions occur<br />9<br />
  10. 10. Task Oriented Task Tracking<br />Configure task tracking: YES / YES / NO / NO / YES or NO <br />Parameter 1 = Task Tracking Active <br />Parameter 2 = Work Requires Task<br />Yes – User must be signed on with task<br />No – Tasked assigned after work via pop-up<br />Parameter 3 = Prompt Confirm/Change Task<br />Allows developers to change Task assigned to object as desired<br />Parameter 4 = Task Changes To Match Object being maintained<br />Automatically changes Task assigned to object <br />Parameter 5 = Disable Special Security on Tasks<br />Yes = Normal menu security controls access<br />No = Must be QSECOFR or Partition Security Officer to work with tasks<br />10<br />
  11. 11. Task Oriented Task Tracking<br />Details of Task Oriented Task Tracking<br />Entered tasks are set to OPN<br />Pre-setup or set-up as needed<br />Set task to WRKwhen developer begins work<br />Specific developer can be assigned or use standard group profile (control)<br />Set task to CLS when developer is done testing<br />Developer believes the change is complete<br />Export task to TST environment<br />Make a uniquely named export list for each task<br />Retain the export list & save file / package<br />11<br />
  12. 12. Administrationof Task Oriented Task Tracking<br />Details of Task Oriented Task Tracking (cont)<br />Reset task to WRK for developer rework<br />Developer does rework in development environment<br />Re-export using same save file and task id<br />Repeat steps 3-5 until QA is approved<br />Set Task to FIN (Finished)<br />Releases Objects from Task Lock<br />Import task export list to RFD<br />Import task(s) export list(s) to PRD when ready to deploy into production.<br /><ul><li>Tasks must be exported in sequence of completion</li></ul>12<br />
  13. 13. Tip and Simple Project<br />Create a simple system to track your changes<br />Files<br />Request Master<br />ID - Via autonum {Becomes task ID}<br />Status (Requested, Approved, Working, QA, Finished, In production) {May be a table}<br />Requester {May be a table}<br />Dates (requested, assigned,QA, Production)<br /> Short Description<br />Request Detail<br />ID<br />Sequence Number<br />Long Description<br />13<br />
  14. 14. Tip and Simple Project<br />Create a simple system to track your changes <br />Simple Header and Detail Program(s)<br />Good first VLF or CRUD Wizard application <br />(Use the VL Framework or CRUD Wizard)<br />14<br />
  15. 15. Repository Synchronization<br />Windows Client Development with IBM iMaster Repository (Only)<br />Allows for automatic propagation from IBM ito non-iSeries repositories<br />Via Host Monitor<br />New Action 33 on IBM iallows changes made on IBM ito be propagated<br />*ALL is Valid<br />Used for Group based development<br />Requires Discipline to make it work<br />15<br />
  16. 16. Repository Synchronization<br />Benefits<br />Keeps all development PCs in sync<br />Allow you to keep a test PC in sync<br />Be Careful<br />Will load checked-in objects even if they are not working<br />can make testing difficult<br />It will load all changes before it allows you to check-in<br />It may take time to simply check in a single change you have made<br />Remote developers may have long waits while connecting<br />16<br />
  17. 17. Administration for Development<br />Deployment Options<br />IBM iServer w/ 5250 Clients<br />IBM iServer w/ Windows Rich Clients<br />IBM i w/ Browser based clients<br />Windows Server w/ Windows Rich Clients<br />Windows Server w/ Browser based clients<br />VL for Linux (Red Hat or SuSE)<br />no character base Unix Solution <br />Linux Server with Browser based clients<br />Linux Server w/ Windows Clients<br />17<br />
  18. 18. Deployment Options<br />IBM i<br />Export / Import<br />High Speed Export / Import<br />Deliver to<br />Windows<br />Deployment Tool<br />Templates<br />Server Objects<br />Client Objects (Thick vs. Thin) <br />JIT<br />Linux<br />Deliver to<br />18<br />
  19. 19. Sample Programs for Moving Data From IBM i to Windows<br />19<br />FUNCTION OPTIONS(*DIRECT)<br />*<br />DEFINE FIELD(#W_PASSWD) TYPE(*CHAR) LENGTH(10) LABEL(&apos;Password&apos;) INPUT_ATR(ND)<br />DEFINE FIELD(#W_RTNCDE) TYPE(*CHAR) LENGTH(2) LABEL(&apos;Return Code&apos;)<br />DEFINE FIELD(#W_SRVNAME) TYPE(*CHAR) LENGTH(10) LABEL(&apos;Target Sys Name&apos;)<br />DEFINE FIELD(#W_CALLFUN) TYPE(*CHAR) LENGTH(10) LABEL(&apos;Calling Func&apos;)<br />* <br />REQUEST FIELDS(#USER #W_PASSWD #W_SRVNAME #W_CALLFUN)<br />* <br />USE BUILTIN(DEFINE_OS_400_SERVER) WITH_ARGS(AS400SRV #W_SRVNAME N) TO_GET(#W_RTNCDE)<br />USE BUILTIN(CONNECT_SERVER) WITH_ARGS(AS400SRV #W_PASSWD) TO_GET(#W_RTNCDE)<br />* Define and connect Other server here, if destination<br />* system is not local DB<br />* Function calls to access to server files<br />CALL PROCESS(*DIRECT) FUNCTION(#W_CALLFUN) EXIT_USED(*NEXT) MENU_USED(*NEXT)<br />USE BUILTIN(DISCONNECT_SERVER) WITH_ARGS(AS400SRV) TO_GET(#W_RTNCDE)<br />* Disconnect Other server here<br />
  20. 20. Sample Programs for Moving Data From IBM i to Windows<br />20<br />FUNCTION OPTIONS(*DIRECT)<br />* Define work fields<br />* Delete local data if there is any<br />SELECT FIELDS(*ALL) FROM_FILE(FILEA)<br />DELETE FROM_FILE(FILEA)<br />ENDSELECT<br />* Connect file - for the first record<br />USE BUILTIN(CONNECT_FILE) WITH_ARGS(FILEA AS400SRV)<br />SELECT FIELDS(*ALL) FROM_FILE(FILEA)<br />* Disconnect file<br />USE BUILTIN(DISCONNECT_FILE) WITH_ARGS(FILEA AS400SRV)<br />* Insert connect_file BIF here to connect file on the<br />* Other server, otherwise, it inserts to local DB<br />INSERT FIELDS(*ALL) TO_FILE(FILEA) VAL_ERROR(*NEXT)<br />* Insert disconnect_file BIF here to disconnect from Other server file<br />* Connect file - for the next record<br />USE BUILTIN(CONNECT_FILE) WITH_ARGS(FILEA AS400SRV)<br />ENDSELECT<br />RETURN<br />
  21. 21. Reference Documents<br />LANSA for IBM iGuide<br />Sections <br />5.4 What is Task Tracking<br />5.5 How to Invoke the Work With Tasks Facility<br />5.12 Exporting and Importing<br />Internal Database & System Utilities<br />Sections<br />3.65 DC@F73 - TTS Export/Import File for External Systems<br />3.66 DC@F74 - TTS Object Register<br />3.67 DC@F75 - TTS Task Definition Log<br />3.68 DC@F76 - TTS Object Event Log<br />3.69 DC@F77 - TTS Export/Import Log for External Systems<br />21<br />
  22. 22. Questions<br />22<br />

×