Thursday, February 9, 2017

Understanding the unique ID in the WebLogic Server JCA adapter plan files

Have you ever wondered where Oracle WebLogic Server gets the strange unique ID you see in the JCA adapter plan files?

<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
  <application-name>FtpAdapter</application-name>
  <variable-definition>
    <variable>
      <name>ConfigProperty_ControlDir_Value_14745947429170</name>
      <value>/u01/fmw1221/user_projects/apps/soa_domain/fadapter</value>
    </variable>
    <variable>
      <name>PoolParams_ConnectionCreationRetryFrequencySeconds_14865793562922</name>
      <value>60</value>
    </variable>
    .
    .
    .

The number is "epoch time" plus "sequential ID".

To get the epoch time on a unix server:

oracle@soahost1:/home/oracle> date +%s
1486588928

The sequential ID is the 4 digit number following it.



Applicable Versions:
  • Oracle WebLogic Server 11g
  • Oracle WebLogic Server 12c



No comments: