RPGMail Enterprise (RME) User Manual
Contents
1. it provides no immediate benefit to Aaron Bartell That is why Aaron has decided to create a Enterprise that builds on the feature set of the original RPGMail Because Aaron is a believer in open source and the ability for a company to have full control of software in their shop he has determined to keep RPGMail Enterprise open source This means that when you purchase the Enterprise version you will not only receive the runtime Java and RPG programs but ALSO the complete source code Features Send email quickly and easily from your RPG program Authentication SSL Read receipts Email priority i e HIGH NORMAL LOW Single JVM in batch This significantly improves performance since there is only ever one JVM running on the machine for RPGMail vs having each signed on job require one Email log tables so you can see everything that is being sent out from RME Unlimited email attachments Unlimited email recipients Special ease of use API s for those times where you just want a single line of code to send an email see API RME_simple Page 2 RPGMail Enterprise User Man Requirements ual for version 0 01b RME was created on a AS 400 running V5R3 of OS 400 This version of RME requires at least V5R1 of the operating system The licensed programs required on your machine are as follows 5722JV1 Java Developer Kit 1 5 installed 5722SS1 OS 400 Portable App Solutions Environment requir2. RPGMail Enterprise User Manual for version 0 01b RPGMail Enterprise RME User Manual for RME_v0 0ib 2009 12 14 www MowyYourLawn com Copyright 2009 Bartell Software QUESTIONS ABOUT THIS MANUAL CONTACT aaronbartell mowyourlawn com Page 1 RPGMail Enterprise User Manual for version 0 01b Table of Contents SUMIMAl Ys ieetesind sets sas cede deacons san dcedebubd vans san deaideb und cede sun dbedeb und tde sau dbdebandtede sau dbadebana cede saedeae canes 2 FEATURES 53 ocean yi stan a yiteruigs vie iaaale ayer wae ye meek tity E ate ered te aan E a peu EE ET EE maior ructe oka tats 2 REQUIFEMENES aerie onari siana A AAA eae tence TAARA RA sine CencewneGeded ARRERA AARAA SARRAR TARRENI AANER EAIA EREA 2 Installand COMPQUIE ri rainei ia edges dads Ain a Liia aE AiE nAAL SiE anA PETRE Lide E aAa En A nRa SETE 3 Start Java Processiss n Aceh A ORO R R ORO OER RO EA AREE 4 End Java PrOCES Simeria annaa e Aaa a a A E Ea ENE a AEN ENEA 5 SC EEEE E E E E 5 B PAIF o A N 6 Rebuild and Deploy J Vassigi serech sanega aaraa EEE AE REEE AEEA AAA ADER 6 LOGS and Debug diN g a T a A N AA EA ds tea dea Debate N EAEE NEETER ia 7 Summary RPGMail Enterprise RME is a follow on tool to the original RPGMail tool created by Aaron Bartell of www MowYourLawn com Through the eight years of RPGMail s existence there have been a number of updates made but because it is a free and open tool it is hard to justify time to update the tool since
3. ed by JDK 1 5 Install and Configure The following is taken verbatim from the readme txt 1 Issue the AS 400 command CRTSAVF FILE QGPL RME file included with the zip file download 2 FTP the file RME from your PC to the AS 400 in BINARY mode H into the save file RME in library QGPL 3 Issue the AS 400 command RSTLIB SAVLIB RME DEV SAVF SAVF QGPL RM 4 Issue the AS 400 commands MKDIR java MKDIR java rme m pan 5 FTP the following files to the AS 400 in binary mode to folder java rme Note that you MUST use binary mode when FTPing otherwise you could get unexpected results because there will ben that renders some jars useless activation jar mail jar jt400 jar RPGMailEnt jar 6 Configure mail server Update the the DFT record in table RM server s information E an attempted E BCDIC conversion ESVR to have your email 7 Issue the AS 400 command to start the Java portion that runs in QBATCH Page 3 RPGMail Enterprise User Manual for version 0 01b ADDLIBLE RME CALL RME STRRMEEZ The following screen shot shows a sample of table RMESVR DFT entry If your SMTP server doesn t require authentication then you should specify an F in the Authenticate column Page 4 RPGMail Enterprise User Manual for version 0 01b Flow of Processing The following image depicts the f
4. ill be retained within the DB2 tables and data queue in a wait state for the Java batch process to start There are two methods of starting RME The first and more laborious is invoking the STRRME command which accepts parameters to allow you to alter the various aspects of how it will run The alternative and preferred method is to invoke the STRRMEEZ command which doesn t require any parms The contents of STRRMEEZ contains a call to STRRME where are of the parms a pre filled in This is very useful because entering the Java classpath CLSPATH parameter is error prone and tedious The following can be used to start the Java process using the STRRMEEZ command ADDLIBLE RME CALL RME STRRMEEZ After starting the Java batch process you should see the following two jobs in your batch subsystem Subsystem Job User Type CPU Function Status QBASE QSYS SBS 0 DEQW QJVACMDSRV AARON BCI 3 5 PGM QJVACMDSRV RUN RMERUNJVA AARON BCH 0 CMD RUNJVA TIMW End Java Process When you want to end the Java batch process you can utilize the ENDRME command The ENDRME command doesn t take any parameters and can be invoked as follows ADDLIBLE RME CALL ENDRME Invoking ENDRME will create a data queue entry that when received by the Java batch process will end it gracefully Note that you could also end the two Java batch jobs using option 4 in WRKACTJOB and it would be detri
5. in your RPG business logic program Rebuild and Deploy Java Coming soon Logs and Debugging Logging aka debugging is available in RME as a mechanism to do problem determination Logs are stored primarily in RMELOG by both the RPG and Java processes but if the Java process isn t able to connect to the IBM i to write records to the log then there will be a file created at the root of the machine that will store debugging information The format of that file will be rme_debug_CCYY Mon DD log If you are running into issues with the Java process successfully starting then what I do is start it from Qshell because that allows for Java s standard output to be sent directly to your green screen The following two steps describe how to do that Step 1 Do a STRQSH from the regular green screen command line Step 2 Paste the following string onto the Qshell command line and select the lt enter gt key Page 8 RPGMail Enterprise User Manual for version 0 01b QIBM ProdData Java400 jdk15 bin java cp java rme java rme activation jar java rme mail jar java rme jt400 jar java rme RPGMail Ent jar com mowyourlawn rme RPGMailEnt localhost CURRENT CURRENT RME By default RME should be configured for debug as shown in the below screen shot Use a value of T or F True or False respectively RECNBR Page 9
6. low of information and processing for a typical email being sent using RPGMail Ente rprise vt 0S 400 Job 1 Invoke RME _ API s to provide it with different information about the email i e To From Subject Body etc 2 Each time an RME API is called the values are stored in DB2 tables for later use 3 When RME _send is invoked by your program a record is written to the DQRME data queue for that particular email 4 The Java process has been waiting on the data queue this whole time and now receives in the entry that was just written 5 The Java process queries the RME DB2 tables to retrieve the email related data 6 The Java process uses the JavaMail API s from Sun to make a call to your email server This can be a local or remote email server 7 After the email is sent the Java process will update the status in the RME DB2 tables and respond to the data queue Note that you can configure it so that your RPG program doesn t wait for a response from the Java process because that could be a needless wait for the user 8 The RME_send API receives the response back from the data queue 9 Control is passed back to your program Page 5 RPGMail Enterprise User Manual for version 0 01b Start Java Process For emails to be sent out there is a Java batch process that needs to be started Note that the RPG side can be invoked without the Java batch process started and the emails w
7. mental Page 6 RPGMail Enterprise User Manual for version 0 01b Examples The example RPG program can be found in source file RME EXAMPLE T1_RME It has also been included here for reference Program T RME Author Aaron Bartell Descr Send a simple email using the DFT RMESVR entry Compile CRTBNDRPG PGM RME T1_RME SRCFILE RME QRPGLESRC SRCMBR T1 RME DBGVIEW ALL iaaa Sie el ete ee a a ot gee Steer Fee ae wie oS ae a Sie a le Eg ein eS eae Se eS Seen H dftactgrp no bnddir RMEBND copy aqrpglecpy RME copy qrpglecpy Error D gUId S 15p 0 D gErr ds likeds Error Info inz D gProp ds likeds RME Prop inz D nl c const x 0D25 D bdyTxt S 1024a varying free monitor gProp svrid DFT gProp sbj Is your fridge running gProp bdyCntTyp RME_TEXT gUId RME_init gProp RME_addHdr gUId RME Prty RME HIGH Set as a high priority email RME_addAdr gUId RME_FROM myname company com RME_addAdr gUId RME_TO somebody othercompany com bdyTxt My first rpg email app nl This is the next line RME_addToBdy gUId bdyTxt RME_send gUId gErr on error gErr Error_catch endmon inlr on end free Page 7 RPGMail Enterprise User Manual for version 0 01b DB2 Tables RMEADR This table holds all of the email addresses of an email It is associated to RMEMAIN using the PID column RMEATCH This table holds all of
8. the email attachment locations associated with an email It is associated to RMEMAIN using the PID column RMEBDY This table holds the email body associated with an email It is associated to RMEMAIN using the PID column RMECFG This table holds the configuration values that are used by both the Java and RPG processes at runtime RMEHDR This table holds header level name value pair information that is associated with an email It is associated to RMEMAIN using the PID column This is a generic table that could have any number of email headers applied to it For example the X Priority name and value are placed in here to give emails the High Normal Low priorities that you see in Outlook RMELOG This table holds all of the logs associated with an email It is associated to RMEMAIN using the PID column If debugging is turned on in table RMECFG then this table will be written to during the email process RMEMAIN This table is the entity that all other email tables stem from It contains the status of the email being processed the server id that is to be used to send the email the subject the body content type i e text plain and whether or not the RPG process should wait for a response RMESVR This table holds the configuration of an email server that will be used to relay mail traffic from RME There should always be a record in here with a key value of DFT which will be the default SMTP server used if none is specified
Download Pdf Manuals
Related Search