Restricting The EnterpriseOne Evironment On The JAS Server
Filed under: E1Tips, EnterpriseOne - JAS (Java Application Server), JVM, Java, Java Application Server (JAS), Tools Release, enterpriseone, oracle, websphere
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://<%=redirectTargetURL%>"><%=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, websphereHow To Build A SRVPGM Using The Command Line
Filed under: *SVRPGM, EnterpriseOne - General, IBM i/System i/iSeries/AS400, Tools Release, enterpriseone
The other day we had an issue with building a full package for one of our EnterpriseOne installations. The issue was related to not having the same tools release active on both the Deployment Server and the Enterprise Server.
However, I found something rather interesting. You can build an individual package DLL or SRVPGM on the System i (AS400, iSeries, i) using the command line.
According to Oracle Support Doc ID 630044.1 you could use the CRTCMOD command. However, this may error because “any object that has a #include for jde.h will not be found”.
The correct steps you must use to compile a DLL or SRVPGM using the command line is below:
- Add the EnterpriseOne system library using the following:
addlible e811sys
- If you wished to build the CFIN SRVPGM, run the following command:
call builddll '/oneworld/packages/<packagename>/text/cfin.txt'
Hopefully, this will help you if you ever need to build a DLL or SVRPGM using the command line.
Tags: *SVRPGM, enterpriseone, EnterpriseOne - General, IBM i/System i/iSeries/AS400, Tools ReleasePresentations from Oracle OpenWorld 2009
Filed under: Oracle OpenWorld, Tools Release, Weblogic, oracle, oracle application server, websphere
JD Edwards and Oracle Application Integration Architecture: One Powerful Combination
Maximize your JD Edwards EnterpriseOne investment with Tools and Technologies
The Benefits of Running JD Edwards EnterpriseOne on the Oracle Technology Stack
Choosing the Right Technology Stack for JD Edwards EnterpriseOne
Batch Version (P98305W) Version Error
Filed under: EnterpriseOne - General, EnterpriseOne - Install/Upgrade, Tools Release, enterpriseone
After our latest tools release update there was a special instruction that I forgot to do on one of the environments. It was to delete all versions of the Batch Versions (P98305W) application.
Usually, there will be just one version: ZJDE0001.
Well, since I forgot, to the left is the error that you might get if you dont do it. The second image is the Interactive Versions screen that you will need to use to delete the version.
Tags: batch version, e1, enterpriseone, EnterpriseOne - General, EnterpriseOne - Install/Upgrade, jde, Tools Release, Tools Release, version, versionsEnterpriseOne Javascript Error Causing Errors In Internet Explorer
Filed under: EnterpriseOne - JAS (Java Application Server), Firefox, Internet Explorer, Javascript, Tools Release, enterpriseone, typeahead, websphere
We recently went live with Employee Self-Service. In doing so, we no longer send employees their direct deposit pay stub. Over the last few days we were notified that some employees were unable to view the paycheck details.
We began troubleshooting the issue with looking at the usually culprits:
- Browser used (Firefox doesnt work with EnterpriseOne Tools Release 8.97)
- Browser security settings (EnterpriseOne & IE7)
- Browser add-ons/plug-ins/extensions
However, nothing seemed suspect.
So, I put on the Web Developer Hat (dont tell Charlie) and started troubleshooting. I found that there was a Javascript error in Internet Explorer. I tracked down the offending file an commented out the code.
The Javascript file that I changed was /js/JDEDTA.js.
The specific line that was causing the problem was line 344. I commented out the whole thing because who needs typeahead functionality in Employee Self-Service?
340: this.saveAutoCompleteData = function(){
341: //Hack to make typeahead work in IE
342: /*if(document.all){
343: var formToPost = document.forms[this.formName];
344: window.external.AutoCompleteSaveForm(formToPost);
345: }else if (!this.isSafari){
346: var formToPost = document.forms[this.formName];
347: if (formToPost)
348: {
349: var action = formToPost.action;
350: formToPost.action = "javascript:void(0)";
351: formToPost.submit();
352: formToPost.action = action;
353: }
354: }*/
355: }


