The Oracle skills market has changed more in the last two years than it has in the last two decades. The economic downturn has undoubtedly slowed a significant amount of project churn, which in turn has given a greater transparency of what skills really are in demand, together with a sudden and perhaps harsh view of what skills have been left on the shelf.

Oracle EBS Functional consultants have had a busy time since the new millennium. The demand for these skills led to more people entering these roles without the previously necessary academic credentials. Since the recent economic downturn, many Functional consultants would argue that they have never seen this level of uncertainty before. Functional Core Financials and Oracle CRM consultants have perhaps seen the slowest times of all Oracle consultants, I could name a dozen people in my own network who have thrown in the laptop and moved out of the Oracle world altogether.

Oracle EBS Technical consultants have seen their demand change over the years. While there is still demand for technical EBS skills, Oracle users are using less customisations in their solutions, and we have seen a lot of technical consultants move towards more functional duties.

Throughout the nineties the traditional Oracle consultant was more likely to be a SQL Forms or SQL Reports developer. In a keynote speech in 2000, Larry Ellison announced that “In the future there will be two types of technical Oracle Consultant: a Java Architect and a DBA”. Whilst the Oracle community at the time were sceptical about this statement, it has been heading in that direction ever since: the recent acquisition of Java has been described as “the most important software Oracle has ever acquired.”

Having asked our Consultancy team, our recruiters and our customers what technical skills they consider the most difficult to find, the most common answer is OA Framework and ADF. I have asked the same question for Oracle EBS Financials functional knowledge and the answer is FSAH and E-Biz Tax. Fusion Middleware and SOA/BPEL skills still continue to be in demand.

Whilst there is a distinct shortage in these skills, as well as specialist modules such as Oracle Contracts and Oracle Enterprise Asset Management, we could argue that the term “skills shortage” could appear a little insulting to those who have been benched in recent months (or even years), so perhaps we need to characterise the problem as a “skills transfer” issue.

George Gallant - March 2010

IWMS – The Background

The term “Integrated Workplace Management System”, or “IWMS” (to satisfy our lust for acronyms), originated from a university academic, and was subsequently co-opted by Gartner. Up until recently, Gartner produced an IWMS market assessment, including a Gartner Magic Quadrant, and without a common term like IWMS there would have been no other way to group a load of vendors together in a comparison document.

During their initial analysis of the facilities and real estate space, it was observed that the market was moving from point solutions to integrated solutions. It was also observed that there was a trend toward defining the facilities and real estate domain more broadly as workplace management, to recognise the advent of workplace mobility and the solutions needed to manage the virtual workplace. Thus, the two trends were combined to the single acronym IWMS.

Although it is recognised that the IWMS definition is very broad, and therefore less useful to describe a market that is becoming more industry verticalized, users still need a coherent framework to evaluate vendors and market trends. Many vendors have used the IWMS blueprint provided in the IWMS market analysis containing the Magic Quadrant to enhance their products and re-align their messages.

So why do we call it IWMS?

If you type IWMS into Wikipedia you get the following description:
IWMS is an enterprise platform that supports the planning, design, management, utilization and disposal of an organisation’s location based assets. IWMS systems assist organisations in optimizing the use of workplace resources, including the management of a company’s real estate portfolio, infrastructure and facilities assets. Four of the primary areas of functionality include Lease Administration, Project Management, Space Management and Maintenance Management.

Premiertec have decided to place strategic focus on delivering the IWMS solution to market. They have therefore designed and delivered an IWMS solution which is built on the latest Oracle E-Business Suite R12.1 platform. This incorporates integration between the following modules - Oracle Property Manager, Oracle Projects, Oracle Enterprise Asset Management, Oracle Site Hub, Oracle Service and Oracle Financials applications. Known as the Premiertec Integrated Workplace Management System (PIWMS), this solution supports the entire real estate lifecycle through a complete, end-to-end Real Estate Management solution.

George Gallant - March 2010

Little did we know…

The first crises happened when during deployment WebLogic could not find class oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener. Thanks to this note we realized that we need to open EAR and comment the listener. And then listeners JpsAppVersionLifecycleListener and JpsApplicationLifecycleListener met the same finale thanks to the note . And finally, listener WLLifecycleListener was removed from EAR. With all those removals, the application was tested on the integrated WebLogic Server.

Finally, WebLogic deployer said that application is successfully deployed. Phew… If you think this is it, then listen to this.

We try to access the application. Application, definitely, fails complaining that we provided NULL password for the database. That was a surprise. You cannot define a data source without specifying password to the database schema. We found a note that we need to add certain parameters to JAVA_PROPERTIES in the setDomainEnv.cmd file. It worked on Windows XP, and did not work on Windows 2003. So, the solution was to change how Application Modules reference the database connection. We switched from JDBC URL to JDBC Data Source.

We access the first page of our application which contains both charts and non-graphical elements. Non-graphical elements rendered ok. BINGO!!!! But all charts failed… The log files provided a very interesting error. It was looking for a data source with name jdbc.NAMEDS instead of jdbc/NAMEDS. So, we had to create an additional data source with JNDI name jdbc.NAMEDS.

Finally it worked. It took us a week to figure out all these steps to understand how to deploy the application. I still do not feel comfortable with removal of the listeners. There must be a way to plug in libraries into the setDomainEnd.cmd file for the libraries to be seen.

Our next task is to connect to our applciation via an OCI driver. Stay tuned.

Why does offshore produce such a bad code?

This is not the first time I was asked this question, not to mention myself asking this question. I knew the answer for this question for the last several years, but I did not know how to make change it.

These are my findings.

Most of big consulting companies which I worked with, which includes (call me if you need company names) among others, impose offshore developers onto the project. It means that if you are an on-site technical manager you are given the offshore developers. You are not allowed to screen resumes of developers or pick the developer you want. People are given to you. No wonder they are referred to as ‘resources’; a blind headcount to meet the project plant requirement for full time employees. I do not want to say that individual developers are bad; however, I have a handful of jokes about the questions I was asked by offshore developers whom I asked to be ultimately removed from the project. Even though offshore developers are ‘cheap’ per hour, a non-qualified offshore developer can cost the customer a lot of money via late code deliveries and poor code quality.

For the second reason I will use the same cliché. Most of big consulting companies, which is probably better versed as, most offshore development managers wish to present their development unit as a black box. You throw a functional design onto them, they tell when it will be built and tested and… offshore vanishes into thin air. Any request as to the progress comes back as ‘WIP’. Any code check in the database returns empty results because the offshore development manager claims that they have a local copy of the database. The delivery date comes and goes, and a couple of days later the offshore development manager presents you with something that is claimed to be fully tested code written according to the specification. The reality is… well… we need to start the real build now.

I am sure the story is familiar to many onsite technical managers. It fully describes ‘Why’ offshore development is difficult. The true question is how to make it work.

I happen to work with an offshore model for one of our European customers where I was perceived as an offshore developer (I live in USA). This is the approach I tried to implement which proved to work quite well. A functional consultant throws a functional design to me and I give back the dates when I think the code will be ready. I write the technical design and post it to the central storage for reviews. Then I start coding. This is a quiet time that lasts several days. However, as soon as I have a piece of code that somehow meets the requirements of the functional design, I claim to the functional consultant that code is written. How much time have I spent?.. Maybe 25% of the time allocated to development. The next week or two (depending on the complexity of the design) are nightmare. Functional designer logs one defect after another, even basic tests break, I am called all kind of names… I keep my head down and keep on coding. One week passes, and tests start completing as desired. Functional consultant finds bits and pieces which he/she overlooked and I add it to the code. By the time the time allocated for coding and functional testing passed, the code is in perfect stage, functional consultant is happy with results, and I am being petted on my shoulder for delivering high quality code on time.

This approach does require a level of maturity from both developer and tester. One of the most difficult parts is that bugs, or defects, are natural part of a software development. This is not evil, this is good. This is something which drives average software to perfection. I am always saying that if not a single defect is caught during the first test, then the defect is so deep in the code that it will take many tests to uncover. It also requires a level of patience on the tester’s side as well as understanding that the first cut of software is very raw. So raw that even the developer did not run a single full test scenario. However, from the customer stand point, such approach delivers the solution on time and with quality.

We, at Premiertec, apply this approach not only to Oracle eBusiness Suite projects. Even on short term engagements, like an Oracle ADF custom development project which ran for just over a month, we did bi-weekly customer presentations of the solution not to mention daily code checks and numerous internal demos. This was a remarkable project where the customer was in the United Kingdom, solution architect in USA, and the development team in our near-shore development center in Ukraine.

This was my answer to the question my good friend asked me.

The title of the report and execution date is simple. The parameter reads its values from an independent value set. So, I started to think how to get hold of the value set ID and what table do I need to read for the meaning, etc. And then!!! I recollected my own blog.

The resulting query is here without much explanations.

select fcr.actual_start_date report_start_date
, fcp.user_concurrent_program_name
, fu.user_name submitted_by
, fcr.argument1 parameter_code
, oe_sys_parameters_util.get_value(fdfcu.flex_value_set_id, fcr.argument1) parameter_description
from fnd_concurrent_requests fcr
, fnd_concurrent_programs_vl fcp
, fnd_user fu
, FND_DESCR_FLEX_COL_USAGE_VL fdfcu
where fcr.concurrent_program_id = fcp.concurrent_program_id
and fcr.requested_by = fu.user_id
and fdfcu.descriptive_flexfield_name = ‘$SRS$.’|| fcp.concurrent_program_name
and fdfcu.application_column_name = ‘ATTRIBUTE1′
and fcr.request_id = fnd_global.conc_request_id

apps.xxpt_chain_controller_pkg.execute

into procedure name, package name and optional schema name. To achieve this I had to count the number of dots in the string.

Being naturally lazy, I decided to give Internet a spin and find a ready answer. To my dismay, all the ready-to-go answers were PL/SQL procedures of questionable quality. The ingenuity of developers did not go beyond reading the string symbol by symbol and, literally, counting dots.

If you are interviewing a PL/SQL developer, please, use this example as an interview question with the proper answer as

select length(p_string) – length(replace(p_string, ‘.’)) from dual

The only method which needs to be implemented is

public void runProgram(oracle.apps.fnd.cp.request.CpContext cpcontext)

CpContext provides developer with all attributes of a PL/SQL concurrent program such as output file, log file, and return status plus a database connection. A typical implementation of this method looks like

public void runProgram(CpContext cpcontext) {
try {
// read parameters
// execute business logic
cpcontext.getReqCompletion().setCompletion(ReqCompletion.NORMAL, “Request Completed Normal”);
} catch (Exception ex) {
// report exception
cpcontext.getReqCompletion().setCompletion(ReqCompletion.ERROR, “Error building output file”);
} finally {
cpcontext.releaseJDBCConnection();
}
}

Though this template is small, it does illustrate the key differences between Java and PL/SQL concurrent program.

By default, Java concurrent program completes with an error, unlike PL/SQL program which completes successfully. Hence, it is imperative to set up not only completion in error, but also when program completes successfully.

At the end of the execution of the Java concurrent program, you must release JDBC connection back to the pool.

Reading Parameters

Concurrent program parameters are accessible via method cpcontext. getParameterList. This method returns an instance of oracle.apps.fnd.util.ParameterList class. This class provides an Enumeration interface to access all the parameters passed to the program in the order defined during the concurrent program registration. This class has one interesting drawback. You can read the parameters only once.

Each concurrent program parameter is represented by an instance of class oracle.apps.fnd.util.NameValueType. It is clear from the name of the class that it provides name, type and string value of the parameter. It means that if you have a date value as the parameter to the concurrent program, it will be available to the Java concurrent program as a canonical string.

I found it useful to have a utility that converts the ParameterList into a Map.

static public Map convertParameters(ParameterList parameterList)
{ Map result = new HashMap();
while( parameterList.hasMoreElements() ) {
NameValueType nameValueType = parameterList.nextParameter();

if (nameValueType.getValue() != null)
{
result.put(nameValueType.getName(), nameValueType.getValue());
}
}
return result;
}

Map provides a better controlled access to the list of parameters. The method can be enhanced to recognize the type of the value and convert them from String into BigDecimal or Date.

Reporting Exception

Exception.printStackTrace() does not work here!!!

If you really want the user to see the exception stack, you need to print it into the oracle.apps.fnd.cp.request.LogFile. An instance of this class is available via cpcontext.getLogFile(). This class provides an OutputStream like interface, though it is not an implementation of java.io.OutputStream.

LogFile provides a number of methods to write strings into the output stream like

write(String message, int level)

Here, level specifies the debugging level which can be set from LogFile.STATEMENT to LogFile.EXCEPTION.
In order to report exception to the log file, you can use the following code

StringWriter writer = new StringWriter();
ex.printStackTrace(new PrintWriter(writer));
logFile.writeln(writer.toString(), logFile.EXCEPTION);

Writing Output

The key task of the concurrent program which we are writing is to read the CLOB that contains the file contents and write it into its output stream. The output of a concurrent program can later be accessed by SQL*Loader, other concurrent program or, even, OAF web pages and services outside of Oracle eBusiness Suite.

To access the database, we need to get hold of the database connection. An instance of the connection can received from cpcontext.getJDBCConnection().

The following method retrieves the CLOB from the database as and InputStream which is then converted into a String.

protected String getOutput(Connection connection, BigDecimal primaryKey) throws SQLException, IOException
{
String statement = “select file_contents from xxpt_file_upload_tmp where id = :1″;
String result;
PreparedStatement stmt = null;
ResultSet resultSet = null;
try {
stmt = connection.prepareStatement(statement);
stmt.setBigDecimal(1, primaryKey);
resultSet = stmt.executeQuery();
resultSet.next();
result =streamToString( resultSet.getAsciiStream(1) );
resultSet.close();
resultSet = null;
stmt.close();
stmt = null;
} finally
{
if (resultSet != null)
{
try { resultSet.close(); } catch (SQLException ex) {}
}
if (stmt != null)
{
try { stmt.close(); } catch (SQLException ex) {}
}
try { connection.commit(); } catch (SQLException ex) {}
}
return result;
}

In this code streamToString method read the InputStream into a String.

An instance of oracle.apps.fnd.cp.request.OutFile get be obtained using methof cpcontext.getOutFile(). This class provides OutputStream like interface, though it is not an implementation of java.io.OutputStream. Writing a string into the output is as simple as

cpcontext.getOutFile().write(fileContents);

Submit Concurrent Program from Java

Oracle provides Java classes to submit a concurrent program. Definitely, one can call PL/SQL procedure directly using JDBC connection, though the Java wrapper is much nicer and easier to use.

Class oracle.apps.fnd.cp.request.ConcurrentRequest represents submission of a concurrent request. You can setup optional layouts, notifications, schedule and other attributes available through FND_REQUEST package.

Constructor of ConcurrentRequest class accepts database connection instance as a parameter.
Signature of the method that submits the concurrent request for execution

submitRequest(String application, String program, String description, String startTime, String subrequest, Vector parameters)

mimics parameters of the corresponding PL/SQL procedure FND_REQUEST.SUBMIT_REQUEST. Here, parameters is the vector of String in the order the parameters are specified during the concurrent program registration. If one of your parameters is a Date, it is your responsibility to convert it into the canonical string.

So, the code that submits the concurrent program may look like

protected void submitConcurrentProgram(Number primaryKey, String purposeCode, int orgId, Connection connection) throws IOException, SQLException, RequestSubmissionException
{
ConcurrentRequest request = new ConcurrentRequest(connection);
Vector param = new Vector();
param.add(primaryKey.stringValue());
param.add(purposeCode);
param.add(String.valueOf(orgId));

int reqId = request.submitRequest(”XXPT”, “XXPTCLOBOUTPUT”, “Print CLOB”,null, false, param);
connection.commit();

MessageToken[] tokens = { new MessageToken(”REQUEST”, String.valueOf(reqId)) };
OAException confirmMessage = new OAException(”XXPT”,
“XXPT_REQUEST_SUBMIT_CONF”,
tokens,
OAException.CONFIRMATION,
null);
throw confirmMessage;
}

As you can see, upon successful submission of the concurrent program, we raise a confirmation exception with the request ID.

This post concludes the series. In the course of six installments we learned the overall technical design, how to build OAF based UI to upload a file, how to parse an Excel spreadsheet into a comma delimited file, how to write a Java concurrent program and submit it from an OAF page controller. Everything I was talking about here has been built and is actively being used by our customers.

We already discussed the query which generated globally unique primary key, and creation of a view object PrimaryKeyGeneratorVO based on this query. The method which generates the primary key becomes

protected Number generatePrimaryKey()
{
OAViewObject viewObject = getPrimaryKeyGeneratorVO();
viewObject.setMaxFetchSize(1);
viewObject.executeQuery();
return (Number) (viewObject.first().getAttribute(”Id”));
}

In order to determine the select purpose, we need to walk through each row of purposes in the current range, and locate the one with checked attribute ‘Selected’, since this was the transient attribute designated to work with table single selection. The method is

public String getSelectedPurpose()
{
OAViewObject viewObject = getFileUploadPurposeVO();
Row[] rows = viewObject.getAllRowsInRange();
if (rows.length > 0)
{
for(int i=0; i {
Row row = rows[i];
if ("Y".equals(row.getAttribute("Selected"))) {
return (String)row.getAttribute("LookupCode");
}
}
}
return null;
}

Now, we are ready to store data in the database. We will need the purpose of the upload later when we submit the concurrent program to print the file contents in its output. So, we extract the purpose separately and pass as a parameter to the storage procedure, which now looks like

public Number storeStream(String inputStream, String purposeCode)
{
OAViewObject viewObject = am.getXXPTFileUploadTmpVO();
viewObject.setMaxFetchSize(0);

ClobDomain myClob = new ClobDomain();
myClob.setChars(inputStream.toCharArray());
OARow row = (OARow)viewObject.createRow();
row.setAttribute(”FileContents”,myClob);
Number primaryKey = generatePrimaryKey();
row.setAttribute(”PurposeCode”, purposeCode);
row.setAttribute(”Id”, primaryKey);
viewObject.insertRow(row);
am.getTransaction().commit();
return primaryKey;
}

The method returns the primary key of the newly created record. We will later pass this key to the concurrent program that prints the output of the CLOB into its output.

Stay with us to learn how to write Java concurrent programs.

We assume that users are loading either Excel workbooks or ASCII files, such as XML documents or CSV files. This makes streamToString method looks like this.

protected String streamToString(String mimeType, InputStream inputStream) throws IOException
{
String result;
// check if this is an Excel spreadsheet
if (”application/vnd.ms-excel”.equalsIgnoreCase(mimeType))
{
try {
result = xlsToString(inputStream);
} catch (jxl.read.biff.BiffException ex)
{ // if not, then assume this is an ASCII stream
inputStream.reset();
result = streamToString(inputStream);
}
} else
{ // otherwise an ASCII stream
result = streamToString(inputStream);
}
return result;
}

This method interprets the mimeType of the inbound file, and either reads it as an Excel workbook using method xlsToString(InputStream) or converts it into a string using method streamToString(InputStream). We will omit details of streamToStream(InputStream) method, as it reads characters from the input stream and appends them to a string, and concentrate on xlsToString(InputStream).

The body for this method was borrowed from here. The method interprets the input stream as an Excel workbook and converts each sheet into a comma separated format.

private final static String CSV_SEPARATOR = “,”;

private String xlsToString(InputStream stream) throws jxl.read.biff.BiffException
{
StringWriter stringWriter = new StringWriter();
BufferedWriter bufferedWriter = new BufferedWriter(stringWriter);
try {
WorkbookSettings ws = new WorkbookSettings();
ws.setLocale(new Locale(”en”, “EN”));
Workbook w = Workbook.getWorkbook(stream, ws);

// Gets the sheets from workbook
for (int sheet = 0; sheet < w.getNumberOfSheets(); sheet++)
{
Sheet s = w.getSheet(sheet);
Cell[] row = null;

// Gets the cells from sheet
for (int i = 0 ; i < s.getRows() ; i++)
{
row = s.getRow(i);
if (row.length > 0)
{
bufferedWriter.write(formatExcelCell(row[0]));
for (int j = 1; j < row.length; j++)
{
bufferedWriter.write(CSV_SEPARATOR);
bufferedWriter.write(formatExcelCell(row[j]));
}
}
bufferedWriter.newLine();
}
}
bufferedWriter.flush();
} catch(jxl.read.biff.BiffException ex)
{
throw ex;
}
catch (Exception ex)
{
throw OAException.wrapperException(ex);
}

return stringWriter.toString();
}

Method formatExcelCell is responsible for converting the contents of a cell into the one compatible with CSV file format. Namely

• double each double quote
• surround contents with double quotes if contents contains a double quote or comma
• convert date into DD-MMM-YYYY format

The formatExcelCell method body is

private final static String QUOTE_STRING = “”";
private SimpleDateFormat dateFormatter = new SimpleDateFormat(”d-MMM-yyyy”);

private String formatExcelCell(Cell cell)
{
if (cell == null) return null;
String rowCell = cell.getContents();
// format the date
if ( cell.getType().equals(cell.getType().DATE) )
{
rowCell = dateFormatter.format(((DateCell)cell).getDate());
}
// double each quote
String result = rowCell.replaceAll(QUOTE_STRING, QUOTE_STRING+QUOTE_STRING);
// surround with quotes if comma or quote is present
if (result.indexOf(CSV_SEPARATOR) >0 || result.indexOf(QUOTE_STRING) >0)
{
result = QUOTE_STRING + result + QUOTE_STRING;
}
return result;
}

Here we reached the point when the incoming stream is tested to be an Excel workbook, and if so, converted into a comma separate stream. Otherwise, it is assumed that the incoming file is an ASCII stream.

Our next task is to store the contents in the database. Stay tuned to learn how to write CLOBs using BC4J.

The content for the table comes from a view object FileUploadPurposeVO which is sourced by the query from the technical design. We add to it a transient updatable attribute ‘Selected’ to allow for single table selection.

The content of the uploaded file is stored in the database table XXPT_FILE_UPLOAD_TMP. So, we create an entity object XXPTFileUploadTmpEO and corresponding view object XXPTFileUploadTmpVO.

We also need a primary key generator. The first thought, of course, is to define a custom sequence. I do not like this idea since the primary key here does not need to be sequential; it just needs to be unique. So, the sequence will be an extra custom database object without a very good need. We can also define or reuse a document sequence. However, this is a lot of application setups for a primary key which will live only a couple of seconds.

The approach I prefer is to use the GUID generated by the database and convert it into a number. The following query generates unique number each run you execute it.

select okc_p_util.raw_to_number(sys_guid()) id from dual

We build a view object PrimaryKeyGeneratorVO based on this query. This view object completes our data model.

There are many examples available over the internet and in the Developer’s Guide on how to build an OAF page. We will skip those here. The relevant assumption is that the table which displays the upload purposes is a single selection table with an action button ‘submitButton’.

This makes the page controller entry point look like this

/**
* Procedure to handle form submissions for form elements in
* a region.
* @param pageContext the current OA page context
* @param webBean the web bean corresponding to the region
*/
public void processFormRequest(OAPageContext pageContext, OAWebBean webBean)
{
super.processFormRequest(pageContext, webBean);
OAApplicationModule am = pageContext.getApplicationModule(webBean);

if (pageContext.getParameter(”submitButton”) != null)
{ processFileUpload(pageContext, webBean, am);
}
}

Method processFileUpload is performing the following tasks

• get hold of the binary file contents
• convert binary file contents into an ASCII stream
• store ASCII in the file in the database
• submit the printing request

The body of this method is

protected void processFileUpload(OAPageContext pageContext, OAWebBean webBean, OAApplicationModule am)
{

// Get hold of the binary file contents
DataObject fileUploadData = (DataObject)pageContext.getNamedDataObject(”fileUploadItem”);
if (fileUploadData == null) return;

String fileName = (String)fileUploadData.selectValue(null, “UPLOAD_FILE_NAME”);
if (fileName == null) return;

String contentType =(String)fileUploadData.selectValue(null, “UPLOAD_FILE_MIME_TYPE”);

BlobDomain uploadedByteStream = (BlobDomain)fileUploadData.selectValue(null, fileName);
if (uploadedByteStream == null) return;

// convert binary file contents into an ASCII stream
try {
String inputStream = streamToString(contentType, uploadedByteStream.getInputStream() );

String purposeCode = getSelectedPurpose(am);
if (purposeCode == null)
{
throw new OAException(”XXRFG”,
“XXRFG_SCR0248_MISSING_PURPOSE”,
null,
OAException.ERROR,
null);
}

// Store ASCII in the file in the database
Number primaryKey = storeStream(inputStream , purposeCode, (UploadAMImpl)am);

int orgId = ((OADBTransactionImpl)am.getOADBTransaction()).getOrgId();
// submit the printing request
submitConcurrentProgram(primaryKey, purposeCode, orgId, am.getOADBTransaction().getJdbcConnection());

} catch (IOException ex) {
throw OAException.wrapperException(ex);
} catch (SQLException ex) {
throw OAException.wrapperException(ex);
} catch (RequestSubmissionException ex) {
throw OAException.wrapperException(ex);
}
}

Stay tuned to go into each of the methods…