Skip navigation

This blog will help you to install the Data Access Driver. Here we are installing DAD on below system configuration

 

Application Release : 9.2

Tools Release            : 9.2.3.3

Database                   : Oracle 12.1.0.2.0

BIP Server Version   : BIP 12.2.1.0.0

          Operating System    : Windows 2016

 

Steps to install the Data Access Driver ( DAD )

 

  1. Install SM Agent
  2. Register the BIP WLS with SM Console
  3. Download latest DAD Tools Release from update center
  4. Upload and Distribute the DAD TR component 
  5. Create DAD Instance
  6. Copy the DAD Tools Release lib files to  to BI lib folder location
  7. Update the setDomainEnv.cmd
  8. Update jdbj.ini
  9. Create a JDBC Data Source in BIP Console
  10. Verify the configuration

 

   Step 1 :  Install SM Agent  

        

  Step 2 : Register the BIP WLS with SM Console

Step 3 : Download Latest DAD Tools Release from update center

      

Step 4 : Upload the Software and distribute the TR to the SM Agent where WebLogic BIP Server is registered

Step 5 : Create a DAD Instance using SM Console 

Step 6 : Extract the DAD Tools Release par file to temporary location and copy to BI Lib folder location

           From Location :

         

    To Location :

        

Step 7 : Update the setDomainEnv.cmd

                

         Update the classpath value with DAD SM Agent config location. Below section of SetDomainEnv.cmd needs to be updated.

 

if NOT "%EXT_PRE_CLASSPATH%"=="" (

if NOT "%PRE_CLASSPATH%"=="" (

set PRE_CLASSPATH=D:\jde_home_dad\SCFHA\targets\DAD\config;%EXT_PRE_CLASSPATH%;%PRE_CLASSPATH%

) else (

set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%

)

)

 

if NOT "%POST_CLASSPATH%"=="" (

if NOT "%CLASSPATH%"=="" (

set CLASSPATH=D:\jde_home_dad\SCFHA\targets\DAD\config;%POST_CLASSPATH%;%CLASSPATH%

) else (

set CLASSPATH=%POST_CLASSPATH%

)

)

 

if NOT "%WEBLOGIC_CLASSPATH%"=="" (

if NOT "%CLASSPATH%"=="" (

set CLASSPATH=D:\jde_home_dad\SCFHA\targets\DAD\config;%WEBLOGIC_CLASSPATH%;%CLASSPATH%

) else (

set CLASSPATH=%WEBLOGIC_CLASSPATH%

)

)

 

if NOT "%PRE_CLASSPATH%"=="" (

set CLASSPATH=D:\jde_home_dad\SCFHA\targets\DAD\config;%PRE_CLASSPATH%;%CLASSPATH%

)

 

Step 8 : Make sure jdbj.ini is updated correctly with your database information

         

Step 9 : Create a JDBC Data Source in BIP Console

 

          Follow the below steps to create a JDBC Data Source

  1. Login into BIP Console
  2. Click on Administration
  3. Now click on JDBC Connection

               

                4. Enter the below information then click on Test Connection

          

              5.Enter the below information then click on Test Connection

 

       Data Source Name      : E1_DAD

       Driver Type                   : Oracle 12c

       Database Driver Class : com.jdedwards.jdbc.driver.JDBCDriver

       Connection String        : jdbc:oracle:enterpriseone://JDV920;

       Username                      : JDE

       Password                       : <JDE User Password>

 

  •      Connection established successfully

         

  •       Click on Apply Save to save this configuration

     

Step 10 : Verify the configuration

 

  •     Login into Server Manager Console and verify whether DAD Instance status is showing as running

         

  •      Login into BIP Console then click on New --> Data Model

         

  •      Click on Add under Diagram tab then click on SQL Query

         

  •      Enter the table name and select the Data Source as E1_DAD then click on Query Builder

         

  •      Select the column ( For example : AN8 ) then click on save button to save the SQL Query

            

  •      Now click on Data - View and see whether we are able to see the E1 data using DAD

         

After domain created successfully on WLS 12.2.1.3.0 , when we trying to start the nodemanager using service or startup script , we are getting the below error message

 

Log file Location : C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\nodemanager

Log file name     : nodemanager.log

 

<Mar 11, 2019 9:13:56 AM UTC> <INFO> <Loading identity key store: FileName=C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\security\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>

<Mar 11, 2019 9:13:56 AM UTC> <SEVERE> <Fatal error in NodeManager server>

  1. weblogic.nodemanager.common.ConfigException: Identity key store file not found: C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\security\DemoIdentity.jks

at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.java:225)

at weblogic.nodemanager.server.SSLConfig.access$000(SSLConfig.java:33)

at weblogic.nodemanager.server.SSLConfig$1.run(SSLConfig.java:118)

at java.security.AccessController.doPrivileged(Native Method)

at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:115)

at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:169)

at weblogic.nodemanager.server.NMServer.getInstance(NMServer.java:134)

at weblogic.nodemanager.server.NMServer.main(NMServer.java:589)

at weblogic.NodeManager.main(NodeManager.java:31)

 

Cause : DomoIdentity.jks file is missing under below location

 

Solution : There are multiple solution for this issue , please refer the document for more information --> FMW/WLS New Configuration with Latest JDK Failing to Start - ConfigException: Identity key store file not found: DemoIdentity.jks (Doc ID 2357811.1)

 

Here we will follow the solution 2 (Re-generate DemoIdentity.jks, then start Web:Logic Server and Node Manager) to resolve our issue

 

Step 1 : Open the cmd prompt as administrator

Step 2 : Using cd command navigate to the location --> C:\Oracle\Middleware\Oracle_Home\wlserver\server\bin

Step 3 : Execute the setWLSEnv.cmd bat file

Step 4 : Now navigate to the directory C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\security using cd command

Step 5 : run the command "java utils.CertGen -keyfilepass DemoIdentityPassPhrase -certfile democert -keyfile demokey -strength 2048 -noskid"

Step 6 : Now run the command "java utils.ImportPrivateKey -keystore DemoIdentity.jks -storepass DemoIdentityKeyStorePassPhrase -keyfile demokey.pem -keyfilepass DemoIdentityPassPhrase -certfile democert.pem -alias demoidentity"

Step 7 : verify whether Demoidentity.jks file is created

Step 8 : Now start the nodemanager and verify the nodemanager.log to verify whether nodemanager process started successfully or not

 

<Mar 12, 2019 3:46:20 AM UTC> <INFO> <Server Implementation Class: weblogic.nodemanager.server.NMServer$ClassicServer.>

<Mar 12, 2019 3:46:21 AM UTC> <INFO> <Secure socket listener started on port 5556, host localhost/127.0.0.1>

 

NodeManager Service started successfully!

This blog will help to download and apply the WLS Path for the issue mentioned in Unable To Access E1 Main Menu Screen After Clicking Login or Stuck on Login Page for JAS Instance Configured with WebLogic Server - 12.2.1.1.0 (Doc ID 2185160.1)

Note : This blog is created based on the below E1 Setup configuration, steps may vary depends upon your setup configuration ( OS and WLS version ..etc).

E1 Setup configuration:

Application Release           : 9.2

Tools Release                    : 9.2.2.2

Application Server version : 12.2.1.2.0

Application Server OS        : Windows 2016 R2

 

Steps Involved in this Installation

  • Download WLS Patch 26197278 from Patch and Updates
  • Pre-Installation Instructions
  • Installation Instructions

 

 

Download WLS Patch 26197278 from Patch and Updates We can download weblogic patches from support portal --> patches and updates. Enter the Patch number as 26197278 then hit search buttonSelect the Patch then click on Download

Save the file in local drive then extract the zip file

 

Pre-Installation Instructions

Before trying to apply the WLS patch , make sure to complete the below tasksSet Environment variable : Add the opatch location K:\Oracle\Middleware\Oracle_Home\OPatch to PATH variable

 

Stop Admin Server , Managed Servers and Node manager

 

Installation Instructions

Follow the below steps to apply the WLS Patch:

  1. Run CMD as administrator user
  2. Type opatch version --> This should display the version as shown in the screenshot
  3. Navigate to the Download location of the Patch  ( C:\Users\Administrator\Downloads\p26197278_122120_Generic\26197278)

 

Now type opatch apply (enter y to continue the installation)

WLS Patch installed successfully! ( Now start the HTML Server and test the issue)

Best Regards,

Karthickrajan K

From Release 9.2 Database Security has been changed. For an installation, all tables delivered by the Platform Pack installer are locked down ( Public Shutdown ) & For an upgrade, only NEW tables delivered by the installer are locked down.

 

Here I am using the Oracle Database , for explaining the concept.

 

Platform pack

 

When we run the 9.2 Platform pack for the installation/Upgrade , we will provide the Admin Role & End user Role as JDEADMIN & JDEUSER in the OUI.

Proxy user :  JDE

 

Platform Pack Installer assigned the Database Role JDE_ADMIN & JDE_ROLE to the Proxy User JDE.

 

For the Other Schema ( users )

 

Platform Pack  Installer assigned the JDEUSER and JDE_ROLE to the other DB schema/user ( DV920, SY920, OL920, SVM920, PS920,TESTDTA,TESTCTL …..etc)

JDE_ROLE  Permission in the Database

 

JDE_ROLE has the below permission in the Database, Because of that E1 Users are able to make the connection with Database and able create a Table & View in the Database.

 

Data Source DB Permission

The main change in the E1 system from  9.2  is below, For example :  Business Data – Test ( TESTDTA)

 

For an Install

 

JDEADMIN & JDEUSER has the Alter, Delete , Insert, Update, Select Permissions for the each table which was created by platform pack on TESTDTA. Because of this E1 users are able to fetch the data , add the data, update the data, delete the data in the Database.

 

All other E1 Data Sources (DV920, SY920, OL920, SVM920, PS920,TESTDTA,TESTCTl  …..etc) also having the same DB Permission.

 

For an Upgrade

 

For an upgrade, only NEW tables delivered by the installer are locked down. The installer does not lock down the logic artifacts during the Platform Pack execution - only the tables.

Note : This is called as Public shutdown. If other application is using your main Database other than E1 then that DB user will not be able to access the E1 Data.

 

What is benefit of the DB Security application ( P986117 ) ?

 

P986117 is simply used for record keeping and enables access to the database without having to ask the database administrator to create a database role and login credentials.

 

For Example : If we want to create a E1 User with read only access ,

 

Before 9.2

 

  • we  need  to create a DB user with Read only permission in DB with a help of DB admin
  • we need to create a System user in JDE .
  • Assign the system user to E1 user

 

From 9.2


Note : Above method also work for 9.2 but From E1 we can do this task with a help of DBA administrator

  • we need to open the application P986117 by login into JDEPLAN ( before workbench)
  • Create the Enter the DB user name ( For example : E1Read ) and assign the permission for all the Data Source

  •   Run the Workbench
  •   We need to create a System user in JDE .
  •   Assign the system user to E1 user

 

Installation Workbench  ( install/Upgrade) will take care the DB user creation and assigning the DB permission in the Database. No need of DB admin to do the task.

 

Record Keeping Purpose

 

For the default installation enter the below two records in P986117 for all the E1 Data Source in P986117 before running the workbench (As per the attached guide ) but I think its just for record keeping purpose so I entered the records using web client (once installation is completed )

For More information

 

Guide : https://docs.oracle.com/cd/E53430_01/EOTSC/datasource_security.htm#EOTSC987

 

Learn jde : https://apexapps.oracle.com/pls/apex/f?p=44785:141:15740944425770::::P141_PAGE_ID,P141_SECTION_ID:343,2574#DBSecurity

 

Impact of missing Enhanced Database Security

 

l have seen the below scenarios where customer faced the issue if this DB privilege were not set properly

 

Case 1 : During the Upgrade ( Install/Upgrade )

 

When customer upgrading the E1 from old release to new release using install/Upgrade method ( Opposite to supported same machine upgrade ) , customer have to refresh the TESTDTA & TESTCTL from old release DB to 9.2 DB .

 

In this activity, if customer drops the TESTCTL and TESTDTA in the 9.2 DB and created the schema from old release. DB Role JDEUSER & JDE_ROLE will not be assigned and missing this permission will leads to Table conversion failure.

 

E1: UPG : Table Conversion Fails While Running the Upgrade Workbench With Error - "OCI0000017 - Unable to execute statement for describe - SELECT * FROM SY920.F0093" (Doc ID 2182159.1)

 

Case 2 : Creating the custom environment ( Without using Environment master or E1 scripts )

 

If customer creating the custom environment by copying the Table, OCM ...etc and creating the custom environment. The Database privilege discussed above will not be applied for the custom environment. This will leads customer in a situation where they cant use the custom environment.

Filter Blog

By date: By tag:

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see https://community.oracle.com/docs/DOC-1022508 for instructions.