EnterpriseOne – JAS (Java Application Server)

3 Ways To Find Your Oracle Weblogic Version

There are at least 3 different ways to find the version of Oracle Weblogic Server that you are running:

  1. Using the registry.xml file located in your MW_HOME directory.
    • example: /u01/weblogic/Oracle/Middleware or E:\Oracle\Middleware
    • Look for a line similar to:
      <component name="WebLogic Server" version="10.3.4.0" InstallDir="/u01/weblogic/Oracle/Middleware/wlserver_10.3">
  2. Using the .product.properties file located in your WLS_HOME directory.
    • example: /u01/weblogic/Oracle/Middleware/wlserver_10.3 or E:\Oracle\Middleware\wlserver_10.3
    • Look for a line similar to:
      WLS_PRODUCT_VERSION=10.3.4.0
  3. Using the Oracle Weblogic Server Administration Console
    • Use the left hand menu to navigate to Environment -> Servers.  Then, click the [Monitoring] tab. You should see a screen similar to the one below:
      Oracle Weblogic Server Administration Console

EnterpriseOne Business Services (BSSV) Error: Security Token Failed To Validate

Every once in a while we get the following error on a system that interacts with EnterpriseOne using business services (BSSV).

Security token failed to validate. weblogic.xml.crypto.wss.SecurityTokenValidateResult@2eba8ea[status: false][msg UNT Error:Message Created time past the current time even accounting for set clock skew]

Fortunately, until today, this error was always received when using our test environment and we couldn’t get it to be consistent so it went unresolved. Well, today was the day it hit production. So, after a little research I was able to find the solution:

  1. Login to the Weblogic Serve Administration Console
  2. Click Environment
  3. Click Servers
  4. Click the server you want to work with
  5. Click the [Configuration] tab
  6. Click the [Server Start] tab
  7. Add the following to the Arguments textarea:

Oracle Weblogic Clock Skew

Customize The Alta Look & Feel Of Oracle EnterpriseOne Tools Release 9.1.5

Customize EnterpriseOne Tools Release 9.1.5

At the company I work for, we like to customize some basic things on the user interface of Oracle EnterpriseOne. The most important part of this modification is to better indicate that the user is signed into a non-production environment by changing the header color. With Oracle’s release of Tools Release 9.1.5, EnterpriseOne is now using the Alta UI framework. This brings E1 more inline with Oracle’s other software offerings. This change has caused us to redo our UI customizations and also look at how we are doing them.

Since we have 7 separate installations for 7 different companies/industries, we also like to modify the logo in the upper left corner to display our companies’ names. In the past, I would have created at least 3 sets of modified files (1 for each environment). That’s 21+ sets of files because some of the companies have more than the standard 3 environments. You’ll notice from the image above that I changed the header color to purple and the corner image to some text.

Since I work in IT and can’t stand repetitive tasks, I don’t like having different files for different companies.  Also, it would be much easier to maintain and easier to remember to make the modification when upgrading, if the companies could all just use the same files.

So, to make that happen, I modified the e1.js file. This file is located in a directory on your JAS Server similar to the following:

I tried to use some comments within the Javascript, but if you need some help, either let me know or contact your friendly neighborhood web developer and they should be able to walk you through it and make any changes that you would like.

Allow Firefox & Chrome To Access Restricted Ports

When separating WebLogic E1 JAS instances we usually end up using odd port numbers.  Sometimes, we use ports that have been put on a restricted list by both Firefox and Chrome. 

Below is a list of the ports that are blocked and the service that is the reason for it being blocked:

1 – tcpmux 7 – echo 9 – discard 11 – systat
13 – daytime 15 – netstat 17 – qotd 19 – chargen
20 – ftp data 21 – ftp control 22 – ssh 23 – telnet
25 – smtp 37 – time 42 – name 43 – nicname
53 – domain 77 – priv-rjs 79 – finger 87 – ttylink
95 – supdup 101 – hostriame 102 – iso-tsap 103 – gppitnp
104 – acr-nema 109 – POP2 110 – POP3 111 – sunrpc
113 – auth 115 – sftp 117 – uucp-path 119 – NNTP
123 – NTP 135 – loc-srv / epmap 139 – netbios 143 – IMAP2
179 – BGP 389 – LDAP 465 – SMTP+SSL 512 – print / exec
513 – login 514 – shell 515 – printer 526 – tempo
530 – courier 531 – chat 532 – netnews 540 – uucp
556 – remotefs 563 – NNTP+SSL 587 – submission 601 – syslog
636 – LDAP+SSL 993 – IMAP+SSL 995 – POP3+SSL 2049 – nfs
4045 – lockd 6000 – X11    

For more detail about this you can visit Mozilla’s website.

We ended up using ports 81-89.  As you can see in the table above, port 87 is listed because of a service called “ttylink”.  Below are the steps that you can take to “whitelist” any port you want.  However, I would recommend not using the list of restricted ports.  It is much easier than going through these steps with all of your users or maintaining a Windows Group PolicyWindows Group Policy.

Firefox:

  1. Type the following URL into Firefox: about:config
  2. Create a string setting called: network.security.ports.banned.override
  3. Give your new setting a value of “87”.  You can also include a comma separated list, a range or a combination of both:  87, 150-300, 350, 400, 450-500

Chrome:

  1. Modify your shortcut to Chrome by changing the “Target” field to look something like:
    “C:\Program Files (x86)\Google\Chrome\Application\chrome.exe”
    –explicitly-allowed-ports=87