denise luther senior it consultant [email protected] practical technology enablement with...
TRANSCRIPT
Denise LutherSenior IT Consultant
Practical Technology Enablementwith Enterprise Integrator
Denise LutherProfessional Experience
• 30+ Years in Information Technology
• 5 Years XA Experience
• Software Design and Development
MAPICS Expertise
• Enterprise Integrator Trainer
• Technical Strategies for working with XA
Recent Customer Success
• Saia-Burgess – Implemented custom supplier web portal using Enterprise Integrator and System-Link
My technical background in the iSeries/XA environment
allows me to help IT professionals
implement new technologies for continued business
success .
Agenda
• Data Sources
• Transaction Broker
• Transaction Objects
• Host Jobs and Reports
• Header/Detail Relationships
• Managing Environments
• Add polish to your applications
Data Sources•Other Platforms•Files on another iseries•Files in another XA environment
• Acquire drivers from the database provider Place them in /MAPICS/driverlib
IFS directory where MAPICS is installed
They will work for all environments
• Drivers are no-charge and can be downloaded from the web
Data Sources - Drivers
•iSeries – already installed•Access – already installed•SQL Server – SQL Server Driver for JDBC
•Oracle – need 9i driver•PostgreSQL – need driver for JDBC3
Platform
Data Sources - Drivers
Data Sources – SQL Drivers
Data Sources
[dsh][dsh]::[port][port]
DatabaseDatabase
[Password][Password]
[user ID][user ID]Database ownerDatabase owner
Data Sources
Display SQL Server• Views, subsets,
sorts
• Full navigation
• Navigation history
• Workbenches
• Code files
• Graph cards
• Compound cards
• Attachments
• Column functions
Navigate to SQL Server table
SQL table from within an object
• Show data in context
• Cards can be external data sources
• Drill-down capability across platforms
Transaction BrokerUser Exit Code Generation
• No source downloads
• More control
• More Exits
• Consistency
• Exported with object
• Enterprise Integrator extends these advantages to your custom objects (no more triggers)
Generate Generate programprogram
Compile Compile programprogram
Display Compile listingDisplay Compile listing
User Exit Source
Transaction Objects
• Transaction vs. object maintenance– Think IM transaction vs. Item Warehouse
maintenance
• Action on a menu• Like IM transaction…
– Has own attributes separate from object– Has own logic separate from object– Can update multiple objects
Transaction Objects
Item Warehouse Maintenance
• Create, update or delete an item warehouse record
• Logic applies to database fields
RM Inventory Transaction• Data is not part of MO or
Item Warehouse objects– Where is Quantity stored?
• Logic is not part of an order object– IM transactions have
unique edits– Doesn’t make sense to
include logic in MO or Item Warehouse maintenance
• Update applies to many objects
Transaction Objects
• Need to be able to transfer inventory from one location to another.
• Allow user to select Item Location records by subset or individual selection, enter the To location, create TRDATA TW transaction record and kick off the PMC process.
• Secure this function and authorize selectively
Transaction Objects
Transaction Objects•Transactions card in object card file•Don’t select a maintenance ID, just click Create
Transaction Objects
Name entered will be default menu text
Transaction ObjectsCard file like Business objects but is independent of Standard actions
AttributesUsed to send information to user exits
Edits
Edit to require entry for To Location
RelationshipsProvides search for location entry
User Exits
User exits structured like standard exits
User exit source to process the transfer
User Exits
AftEXT0043TXN – code to create TW TRDATA record
User Exits
CLOFIL – Send dataq to process transfer
User Exits
Select row(s) for transferClick the toolbar button to execute the transfer
Run Time
• Popup will ask for Transfer To Location• Search provided to lookup valid location
Run Time
• Enter or select location and click continue• User exits will process the TW transfer
• Process from buffer runs from client
Run Time
Secure the actionTo lock down this action independently of the standard
maintenance, Lock and authorize the Task/Subtask Client Extension Object Security Area
• Replacement for Program actions• Allows creating attributes
• date sub-type – forces valid date entry• Discrete domain/Code files• Standard edits• Custom edits for error reporting• Default data generation• Search functionality (relationships)• Process from buffer user exit – code that would
normally in the program action host program
Object transactions
Host Jobs and Reports
• Host Reports and Host Jobs are processes that are invoked from the client to run on the host
• Host Reports typically read data from the server and print a report based on that data • PO Print
• Host Jobs typically perform work that alters data on the server• PO purge
• Add custom Host Reports and Jobs to Business Objects
Adding Host ReportsSelect the Host Processes card and the
Reports sub-card
• Enter the name of the host report on the Create Business Object Host Report prompt
• This is the name that appears on the Host Reports tab
Adding Host Reports
Adding Host Reports General card contains information about
the Host Report
Attributes• Create “attributes” using the Attributes card • Appear as options when the user runs the Host Report
Edits• Standard Integrator - define simple edits on single
attributes• EI - define Custom edits that will be processed by
the server using the Validate user exit
RelationshipsEnable the users to lookup values instead of
directly keying them
User exit programs can be generated and compiled like user exit programs for other types of Business Objects
User Exits
• Host Reports are executed from the Host Print option on that object’s File menu
• List of the available reports for that object positioned alphabetically in the list of available reports
• Attributes that were created in Integrator for the report will show as options (currently in alphabetic order) for the report
• Name attributes to control order in run-time list
Host Reports
Host Reports
Host Reports
Same confirmation and email notification available
• Adding a custom Integrator Host Job to a Business Object is done in the same way as a Host Report
• Use the Jobs tab on the Host Process tabbed card.
• Attributes, relationships, and edits are added in the same way as a Host Report
• User exit programs are the same
Host Jobs
Host Jobs
Host Jobs
• Host Job are executed using the Host Job option on that object’s File menu
• Host job will show up as one of the available jobs for that object in alphabetic order
• Attributes that were created in Integrator for the report will show up as options, currently in alphabetic order, for the job
Using Host Jobs
Using Host Jobs
Using Host Jobs
• Business Object Host Reports/Jobs require some CAS host records in order to correctly process transactions
• Created and maintained automatically during a save to host
• Security authorization record to limit who has access to run the custom Host function
Security class = ‘REPORT’ or ‘JOB’ Security category = EXTxxxxRPT (Host Report)
or EXTxxxxJOB (Host Job) xxxx=extension for host process
• Client Extension Object Security area of CAS Area and task authorizations
Host Records
“Process buffer” user exit– Host process runs in batch– Transaction object runs in client
Process multiple records– Host process presents attributes (options)
once– Transaction object presents attributes for each
selected records (like quick change)Run-time execution
– Host process run from File menu option– Transaction runs from toolbar button
Host Process–Transaction Differences
Header/Detail Relationships• Special 1 to Many relationship• Create custom detail type relationships between
user defined header and detail objects
• Copy transaction copies both header and details• Delete transaction deletes both header and details• Locking header locks corresponding details• Allows detail objects to be created and validated
at the same time as the header• Transactions for changed detail objects include
changed header fields in TRNDTA for use with user exits
• Available for overview cards
Header/Detail Relationships
• Primary object type• Transaction Broker/None Maintenance
Methods• Detail business object must have the
same keys in same order as the header, plus any extra key fields
• Header can have multiple detail business object relationships
Rules
Project Tracking
• Start project tracking from Enterprise Object• Maintenance Card• Maintenance History
Project Tracking
• Create a project for each application or series of object maintenance
Project Tracking
• Select a project each time you save to host• Maintenance history records tells what changed• Project tied to the maintenance
Project Tracking
Improved management for environmentsImport/Export individual objects • Use subsets or selected records to limit
export
Presentation Schemes, Attributes• Colors, Bold Fonts
• Lower Case
Compound Cards• Combine multiple cards, views onto one card• Only contains what user needs to see• Customize Titles and Banners• Use appropriate icon and toolbar buttons
