JAS (Java Application Server)

The EnterpriseOne JAS (Java Application Server) category will include all posts and pages pertaining to the JAS (Java Application Server) of EnterpriseOne.

EnterpriseOne (E1) ERP Employee Self-Service

We are starting a Employee Self-Service project in the next month or so.  The overall goal of which is to provide a place where employees can view/change their personal information: address, phone number, W-4, dependants, etc.  There are many application setup things that need to happen in order for this to be possible.  Luckily for me, I don’t have to worry about the function setup, but am concerned about the technical stuff.

From a CNC perspective, this could be a nightmare.  We’ve done a fairly decent job restricting the sprawl of our system to being very basic: 1 Enterprise Server, 1 Deployment Server, 1 JAS Server.  Ok, maybe only having 1 JAS server isn’t really recommended but there are plans to add to that.

Anyway, there seems to be 4 basic hurdles to clear:

  1. What about the additional users that do not currently use E1?

    Additional users, which have never seen E1 before, will be added to E1.  To create the user profiles, we will either import from the Address Book (R0092) or enter them by hand.  There will also be some security work to setup additional roles to access the Employee Self-Service stuff.  Application support for these users will need to be coordinated with the PC Helpdesk, Human Resources and Payroll departments.

  2. How will the users be presented the application?

    There seem to be 3 choices on this issue: 1) Use the portal.  2) Use the normal UI with a scaled down menu.  3) Setup our own web page that links to the applications using parameterized URLs.

    Here is a quick rundown of why we decided on option 3:

    • Option 1:  adds system complexity; may cause a degradation in performance; lacking current in-house JAVA expertise for UI modifications
    • Option 2:  may confused users by presenting them with an unfriendly menu; no control over the UI
    • Option 3:  greatest control over the UI using current staff expertise; maintains system simplicity
  3. Can the users access it from home?

    Now, this one worried me a little.  However, I know that it can be done using SSL.  I don’t exactly know how to do this, but shouldn’t be too difficult.

  4. What happens to the server during the last week of the Open Enrollment Period when everyone is making their selections?

    There will be about a month out of the year that the system will be very heavily utilized, which may require additional JAS servers.  That means setting up a cluster of Websphere servers, both horizontal and vertical.  I’m not real excited about this either, but I know it can be done.

These three things really shouldn’t be too difficult to tackle, but could definitely cause some issues.

My main concern is numbers 3 & 4.  I really don’t want to add anymore complexity that is required. 

Then, I got wind of a project that was going on with our internet servers and MS SharePoint (I am a secondary administrator for the web servers and like to make sure I know what is going on in that arena).  Anyway, they are testing Microsoft’s Internet Security and Acceleration (ISA) Server.

What is it?  The following is from the ISA web site:

ISA Server 2006 is an integrated edge security gateway that helps protect IT environments from Internet-based threats while providing users fast and secure remote access to applications and data.

We’ve done some preliminary tests and have found that both issues 3 & 4 could be resolved using an ISA server without installing SSL or clustering Websphere.

Not too bad for Micro$oft!

Remove EnterpriseOne (E1) Environment Selection Screen

In our EnterpriseOne (E1) configuration, I force the user to pick what environment they are going to go into before they login by presenting an HTML page that then gives them links to the different environments.

I have each environment on it’s own port, so that I can bring down one environment without disturbing the others.

Anyway, by default, after signing in E1 asks the user what environment they would like to log into. Since I have everything separated, they only get one choice.

The users were annoyed with this “extra” screen that didn’t really provide them with anything. So, I did some research and found a way to remove it on JDEList. I also specified a default role with these settings.

In the JAS.INI file in the WebSphere instance:

[OWWEB]
DefaultEnvironment=JPD811
DefaultRole=*ALL

[LOGIN]
DisplayEnvironment=Hidden
#Options: Show|Hidden|ReadOnly|UseDefault

Hope this helps. It was an easy way to be the Hero-of-the-day…10 minutes…few seconds.

Technorati Tags: e1,enterpriseone,erp,peoplesoft,oracle,jde,jd edwards

iSeries JDBC jt400.jar – {note to self}

Excerpt from a post on JDEList.com by Colin Dawes:

You CAN NOT use the jt400 from the client access folder.

You need to use the jt400 that is on your iSeries. The 2 versions are not the same and you’ll get some hanging if you use the iSeries Access version.

The jt400 on the iSeries is located at:
/QIBM/PRODDTA/HTTP/PUBLIC/JT400/LIB/JT400.JAR

Usually you need to copy this to the following location on Windows:
WebSphereAppServerlib

I say usually because sometimes during the installation prople point the installed to the iSeries Access Path. In this case the WAS variable will be incorrect and you either need to (1) Change the variable in WAS or copy the jt400.jar from the iSeries on top of the jt400.jar that came with iSeries Access.

Technorati Tags: e1,enterpriseone,erp,peoplesoft,oracle,jde,jd edwards