Testing JSP Changes In IBM WebSphere Without ReStarting The Service

This is a follow-up to my previous post “Restricting The EnterpriseOne Evironment On The JAS Server”.

While coming up with my solution to how to restrict users to an environment when logging on to a JAS server that hosted a path code with multiple environments attached to it, I wanted to be able to test my changes “on-the-fly”.  I didn’t want to restart the service every time.

So, that’s when I found the “temp” directory.

• This is the “production” directory:
  C:\WebSphere\AppServer\profiles\default\installedApps\Node01Cell\JPD811_HTML.ear\webclient.war\share
• This is the “temp” directory:
  C:\WebSphere\AppServer\profiles\default\temp\Node01\JPD811_84\JPD811_HTML\webclient.war\share

A file named “_html4env.class” will be placed in there when a user logs in.  It is a compiled version of the “html4env.jsp” file.  So, if you delete that file and make a change to the “html4env.jsp” file or the “_EnvRestriction.htm” file, when a user tries to login WebSphere will compile the “html4env.jsp” file and create a new “_html4env.class” file with your changes.

Tags: E1Tips, enterpriseone, EnterpriseOne - General, EnterpriseOne - JAS (Java Application Server), Java, Java Application Server (JAS), JVM, oracle, websphere

Restricting The EnterpriseOne Evironment On The JAS Server

The organization has a requirement to have a user only login to a certain environment from a certain JAS server instance.

With a basic install of EnterpriseOne, this would be very easy. However, the 2 environments that are required to be separated are build on top of the same pathcode. Within the JAS settings there is a "Path Codes" parameter that allows you to specify which Path Code will be allowed to be accessed from that particular HTML Server instance.

As you can see from the image, there is also a setting for the "Default Environment". However, there is not a setting to specify which environments are allowed to be accessed.

So, I did a little JSP hacking and came up with a way to restrict the EnterpriseOne environments that can be accessed from a particular HTML Server instance on JAS:

The solution involves creating a file that gets "included" into another.

The first file is the one that we created. We called it "_EnvRestriction.htm":

<%
String redirectTargetURL = "erp.mdu.com";       
String mustHaveEnv = "JPDSS811";
if (!(environments.contains(mustHaveEnv))) {
%>
        <tr>
                <td colspan="3" style="font-size:larger;">
                        <strong>YOU DO NOT HAVE ACCESS TO THIS ENVIRONMENT!</strong>
                        <br /><br />
                        You will be redirected to <a href="http://&lt;%=redirectTargetURL%&gt;"><%=redirectTargetURL%></a> in <span style="color:red" id="redirectSpan">10</span> seconds.
                </td>
        </tr>
        <script type="text/javascript">
                function redirect(url, msg)
                {
                   var TARG_ID = "redirectSpan";
                   var e = document.getElementById(TARG_ID);
                   var cTicks = parseInt(e.innerHTML);
                   var timer = setInterval(function()
                   {
                          if( cTicks )
                          {
                                 e.innerHTML = --cTicks;
                          }
                          else
                          {
                                 clearInterval(timer);
                                 document.body.innerHTML = msg;
                                 location = url;          
                          }
                   }, 1000);
                }
                redirect("http://<%=redirectTargetURL%>","")
        </script>
        <style>input{display:none;}label{display:none;}</style>
<%
}
%>

Next we edit the file "html4env.jsp" to include our new file (_EnvRestriction.htm). At about line 172, we include the following right before the <tr> tag:

Please Note: this may not be the best way to restrict environments but it is what we are using. Also, this solution has been successfully used for EnterpriseOne Tools Release 8.97.2.0 & 8.97.2.6. If you are using a Tools Release other than those listed you may need to make adjustments for this solution to work or it may not work at all.

Is there another way to restrict the environment that a user is able to login to when accessing a JAS server if there are multiple environments built on top of the same path code?

Tags: E1Tips, enterpriseone, EnterpriseOne - JAS (Java Application Server), Java, Java Application Server (JAS), JVM, oracle, Tools Release, websphere

Verify That A Version Of Java Is Available

Previously, I wrote about some Java commands that can be used to determine your default Java version.

The following can be used to verify that a certain version of the Java Runtime Environment (JRE) is available on your system.

Tags: enterpriseone, IBM i/System i/iSeries/AS400, Java, JVM, Minimum Technical Requirements, STRSQH

Journaling a Physical File on IBM iSeries Using STRJRNPF

We have a system that needs to interface directly with some EnterpriseOne Files.  This system is written in Java and seems to be very difficult to change any JDBC settings to not use commitment control.

Anyway, to get around this issue, we started journaling the physical file that the JDBC command was trying to update using the following command:

STRJRNPF FILE(PRODDTA/F0911) JRN(OWJRNL/OW_JRNL)

Tags: enterpriseone, enterpriseone, EnterpriseOne - General, ibm, IBM i/System i/iSeries/AS400, iseries, Java, JDBC, JDBC, JDBJ, system i

How To Start/Stop The Managed Agent On AS400

You can start/stop the managed agent from the command line (green screen) by following the steps below:

1. Start the QSHELL by typing STRQSH at the command prompt.
2. Change to the JDE_HOME/bin directory by typing <install_dir>/JDE_HOME/bin.
   *** The <install_dir> refers to the installation directory in the IFS
3. To start the agent enter: startAgent &
   *** The & allows the agent to start as a background job so that it will not stop when you leave the QSHELL
4. To stop the agent enter: stopAgent
5. To restart or bounce the agent enter: restartAgent

You will want to run this in your startup script with a user that has a job queue that is not able to be interrupted.  Because of this, QINTER is not a very good choice.  The user will also need the following permissions: *ALLOBJ, *SAVSYS, *JOBCTL & *SECADM.

Also covered on Oracle’s My Support page ID 659949.1

Tags: *ALLOBJ, *JOBCTL, *JOBCTL, *SAVSYS, *SAVSYS, *SECADM, as/400, EnterpriseOne - Security, Java, jde, oracle, QSHELL, QSHELL, STRSQH

EnterpriseOne Minimum Technical Requirements

Recently, I found that the Minimum Technical Requirements for Oracle EnterpriseOne to be a little difficult to track down. 

So I thought I should create a post about it here so that I don�t have to waste a bunch of time looking for it. 

If I remember I did this, anyway.

 

 

JD Edwards EnterpriseOne Current MTR Index (Doc ID 747323.1)

Application Packs

Application Management Pack

Business Intelligence

Oracle Business Intelligence Publisher

Oracle Embedded Business Intelligence Applications

Business Servers

Business Services Servers

Clients

EnterpriseOne 8.0/Xe

EnterpriseOne Tools 8.9x

Clients Pervasive

EnterpriseOne 8.0/Xe – Pervasive

EnterpriseOne Tools 8.9x – Pervasive

Cluster Servers

EnterpriseOne 8.0/Xe

EnterpriseOne Tools 8.9x

Collaborative Portal

Collaborative Portal 8.0/Xe

Collaborative Portal 8.9x

Crystal Report – Business Objects

Business Objects Enterprise XIR2

Crystal Reports XIR2

Database Software

EnterpriseOne 8.0/Xe

EnterpriseOne Tools 8.9x

Deployment Server

EnterpriseOne 8.0/Xe

EnterpriseOne Tools 8.9x

Disk Space

8.9x Disk Space Requirements

Enterprise Servers

EnterpriseOne 8.0/Xe

EnterpriseOne Tools 8.9x

EnterpriseOne Integration

EnterpriseOne Integration Page

Extended Process Integration XPI

Enterprise XPI Foundation

JD Edwards EnterpriseOne 8.12 Integration Points

Enterprise XPI 8.11 Integration Points

EnterpriseOne 8.11 SP1 Integration Points

Mobile Tools

Mobile Client 8.9x

Mobile Synchronization Server 8.9x

PIM Sync Server

EnterpriseOne Tools 8.9x

Operational Consoles

Plant Manger’s Dashboard Version 8.12

Plant Manger’s Dashboard Version 8.11 SP1

Financial Management and Compliance Console Version 8.12

Financial Management and Compliance Console Version 8.11 SP1

Real-Time Events Server

EnterpriseOne Tools 8.9x

Supply Chain Planning (SCP)

EnpterpriseOne Supply Chaining Planning Page

Third Party Software

WebSphere MQ

Vertex Payroll Tax Q Series

Vertex Sales Tax Q Series

Terminal Servers

EnterpriseOne 8.0/Xe

EnterpriseOne Tools 8.9x

Virtualization

Oracle VM

Web Servers

EnterpriseOne 8.0/Xe

EnterpriseOne Tools 8.9x

Web Services Gateway Server (WSG)

Web Services Gateway server (WSG)

Information Websites

EnterpriseOne Xe

EnterpriseOne 8.0

EnterpriseOne Tools 8.9x

Tags: e1, enterpriseone, enterpriseone, EnterpriseOne - General, IBM i/System i/iSeries/AS400, Java, jd edwards, MetaLink, Minimum Technical Requirements, oracle, oracle, oracle enterpriseone, Oracle Server Manager, version, websphere, websphere, xe

Handy eGen Tweak

In order to shorten the time that it takes to run the eGen process, I modify a couple settings in the gen.bat file.  They modify the memory that is used by the JVM.

• ms128m �> ms512m
• mx512m �> mx1024m

The full line in the gen.bat looks like the following:

• %JAVA_PGM% -Xss1m -ms512m -mx1536m -Ddefault_path=%INI_DIR% -classpath %GEN_CLASSPATH% com.jdedwards.runtime.generator.Generator %1

NOTE: This is on a workstation with 2GB RAM running Tools Release 8.97 and the settings are what I use.  This is not a recommendation from Oracle.

Do you have any tweaks for the eGen process that you use?

Tags: eGen, eGen, enterpriseone, EnterpriseOne - JAS (Java Application Server), Java, jde, JVM, oracle, Tools Release