kernel->kernel is a background process that runs on logic server/ES and performs

specific set of functions and responds to requests from client machine,server and
third party.
jdenet_reserved kernel->used for internal testing.
ube kernel->receives request from client and schedule jobs in job queue. it adds a
record in job table.
security kernel->process security server requests.handles all user profile and
security related tables updates via messaging from COK through bsfns.
lock manager kernel->process Transaction Manager and Lock Manager requests.Lock
Manager is utilized to monitor time/date stamp changes to records.
call object kernel->runs bsfn logic on server based on request from client through
jdenet.
jdbnet kernel->process database requests using client and server.
management kernel
scheduler kernel-handles scheduler application requests
pkg build kernel->responsible for pkg build process
ube subsystem kernel->control the submission of subsystem requests
workflow kernel->handles workflow requests
queue->handles job queue.jobs are launched as per queue configuration in F986130.
xml trans kernel->Enables you to use a predefined transaction type (such as
JDEOPIN) to send information to or request information from JD Edwards
EnterpriseOne.
XML transaction uses interface table functionality.
XML list kernel->Enables you to request and receive JD Edwards EnterpriseOne
database information in chunks.
XML dispatch kernel->Provides a single point of entry for all XML documents coming
into JD Edwards EnterpriseOne.
XML transformation system(XTS)->transform xml doc which is not in E1 to xml doc
which can be processed by E1 and transforms to its original file.
XML service kernel->enable ypu to request events from 1 jde E1 system and receive a
response from another jde E1 system.
XML publisher kernel->handles xml publishing requests
metadata-Processes XML spec access requests.changes xml to c structures that will
be readable by COK.COK is the only kernel to use metadata.
Event notification kernel

zombie->process which are no longer useful.may be created due to database

issue,faulty code or process

middleware-middleware is a layer between os and business applications.

jdenet_n->parent process-a socket based middleware which provides communication
between client-server,server-server.when jde service is started jdenet_n will be
initiated.
jdenet_k->child process

issues we can see in kernels:

database connection issue,network issue,memory issue,for bsfn pointers might be
responsilble,bsfn logic,os problems

troubleshooting xml kernels

check kernel definition in jde.ini file
check that the library name is correct for the platform on which you are running.
Check the maxNumberOfProcesses and numberOfAutoStartProcesses values for the kernel
in the server jde.ini file
If you are using XMLList kernel, check that the LREngine section is correctly setup
in the server jde.ini file, and that the specified path exists.
Also check that the ERP user has write permission to this location.
check xml doc is a well formed xml format. use any XML editor or open the document
in Microsoft Internet Explorer and check for errors.
All input XML documents should have jdeRequest as their root element.
Check that valid user ID, password, and environment are provided in the XML
document.
Check that the request type in the XML document is correct. The allowed request
types are callmethod, list, and trans for XMLCallObject, XMLList and XMLTransaction
kernels.

parameters for kernel in jde.ini file

kernel name->kernel name
dispatch DLL name->identifies name of the library that contains the function to
process the requests received by kernel process.entries are platform specific.
dispatch DLL function->contains name of function to handle messages.platform
specific
maxnumberof process->represents max number of kernel process that can run on
server.
numberof Auto start process->represents the number of kernel processes that
automatically start.number must be less than the maximum number of processes.

inservermanager runtime metrics will give runtime info of kernels.

=================================================================================
central objects->object specs+c code.objects are locaated in central location.specs
are stored in a database server as records.
replicated/pkg objects->stored in xml format in a relational database.created
during pkg build process.
serialized obj->stored in database tables and used by web clients at runtime.
udo->stored in system tables->F9860W - Web Object Master Table,F9861W - Web Object
Librarian Detail

pathcode->points to specific set of objects in a directory.pathode is a set of

environments.
environment->pathcode+ocm combination of business data and code.
environment is a collection of pointers that indicates location of data and
objects.(pointer to data and logic objects).
An Environment is a defined work area and gives a user specific set of parameters
and privileges to work within.
Development environment is defined for undertaking development and customization
related activities and would be accessed by developers and the initial testing
team.
datasource->pointers to data location or server that process logic requests.
defines databases and logic machine configured in onewrold.
types of datasource(10):
OL->points OL tables.only one set per release.has a record for every objects exists
in system and also has one for every objectfor every pathcode in the system.
system->consists technical tables which are used to run jde applications. 1 set
must be required.
DD->stores dd master tables.we will share among all env except Pristine. Pristine
has its own dd.option: 1 for a pathcode
local->defines Enterprsie one client.
Business data->points to business data info.each group of data requires a separate
datasource.
Distributed process->contains info that software identifies logic manchine in the
network.
Server map->enables to create a subset of system tables called server map
tables.these tables are required for each logic server.
control tables->contains udc,menu,nextnumbers
central objects->points to source objects(specs for central objects),user overrides
table.
versions->stores version and PO info.
ocm-ocm directs the system where to find the correct data and logic processing
resources based on environment.
-----------------------------------------------------------------------------------
---------------
Subsystem jobs are jobs that continuously process records from a data queue.
stopping a subsyem->terminates the job when the current processing record is
completed.
ending->terminates the job once all the records are the processed.
softcoding-it contains a value used by bssv to call an external web service.
------------------------------------------------------
generating index for audit enabled table:
first check whether cfr5 column in f9540001 is having 1 or 0 for that table for
required environments
if it is 0 np, if it is 1 make it to 0.
take backup of audit table and normal table. drop view.drop table. generate table.
insert data. generate index to improve performance.update cfr5 to 1.
---------------------------------------------------------------
ocm is a tool which helps to indentify the location of data and business logic.
OCM provides the flexibility to map data, batch applications, and business
functions to a data source, which enables you to coordinate the distributed
processing.
For example, you would map table objects to database data sources and logic objects
to machine data sources
OCM also contains mappings that define where particular types of logic,
specifically business functions or UBEs, will be processed.

how to add/copy/delete ocm

add ocm:
p986110->add->env name,obj name,primary datasource,system role,obj type,data source
mode,secondary datasource(optional),allow QBE.click ok.activate the ocm.ocm is
created.record is
added to F986101 table.
to apply for all objects use default as obj name
primary data source->if mapping is for ube or bsfn select logic ds,for table select
databse ds.
Allow QBE: EnterpriseOne will look at this field to determine if JDEBase uses row-
level record locking.
to test the change logoff and login for client machine,for html clear cache.
copy ocm:
P986110->select the required one->click copy,make changes.click ok.refresh
screen.activate new mapping
deleteL:
select the required one and click on delete
-----------------------------------------------------------------------------------
------
ESU-a bug fix from Oracle.
ASU-new or enhanced code
service pack or tools release-an update to foundation code which will support all
application.
A system map is a table that controls how the users interact with the system
A server map is a table that controls how the enterprise servers interact with the
system
-----------------------------------------------------------------------------------
-
p9601(gh9083)-package build and dep
gh9011-work with servers
p9000-tasks and task relationships
p00950-security workbench
p98616(gh9013)-printer
printer->add printer->platform type, printer model,location,paper type/size,printer
definition language
p986130(gh9013)->job queue
p91300(gh9015)-scheduler application
p98230(gh9081)-omc application
p00241-batch security
P954000-softcoding application
p9540001-work with configuration settings, f9540001->CFR TABLE
p93081-flat file encoding
p951000-bssv property application
P98220W-omw web
p98220-omw
p98220U-udo application
P986110-ocm,F986101 table
p986115(gh9011)->database datasource
gh9053->pathcode
F96225-stores pkg build status
F00942->object path master table-using this we can track set of objects and their
location. this table contains pathcode.
P980042->pathcode master program
P989400-environmet director program
p0094-environment master
-----------------------------------------------------------------------------------
--------
non pd pd
ES 12 22
DB S 2 4
WS 8 17
ais/orch 4 4
bip 1 1
bssv 1 4
-----------------------------------------------------------------------------------
-----------
deployment server:
acts as a central repository. it has code which is not used at run time, so from
this server we will deploy to other machine which will be used at run time.
supports only windows. 1 dep server is madatory.
enterprise server:
supports for windows/linux/iseries
primary run time server.at run time all clients will communicate with es to process
logic.
weblogic console url
http://hostname:port/console
hostname is the machine name or IP address of the host server
port is the address of the port on which the host server is listening for requests
(7001 by default)
webserver:
windows/linux/iseries
-----------------------------------------------------------------------------------
-------
how to clear cache for html server using server manager
login to sm->html instance->runtime metrices->jdbj database cache->select the check
box to clear cache
The following caches are available to be cleared:
Data Dictionary Glossary Text
Data Dictionary Alpha Cache
Row Column Cache
JDBJ Security Cache
JDBJ Service Cache
Serialized Objects
Menu Cache
------------------------------------------------------------------
how to start weblogic from cmd if weblogic is down
login to machine->go to installation path/user_projects/domain/bin,copy the path
open cmd as admin->cd paste the directory and type startweblogic.cmd next
startweblogic.sh
weblogic will be started
to check login to weblogic console
http://host:port/console
how to add weblogic server as a windows service
Create a CreateWLSSvc.cmd file and add the following lines and change as per proj
requirement
SETLOCAL
set DOMAIN_NAME=E1_Apps
set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\E1_Apps
set SERVER_NAME=[AdminServer or Managed Server Name]
set PRODUCTION_MODE=true
set JAVA_VENDOR=Oracle or Sun
set JAVA_HOME=C:\Oracle\JDK_1.7
set JAVA_OPTIONS=-XX:MaxPermSize=350m -Xms32m -Xmx1024m -
Djava.xml.rpc.ServiceFactory=oracle.j2ee.ws.client.ServiceFactoryImpl
call "%USERDOMAIN_HOME%\bin\setDomainEnv.cmd"
call "C:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL

save the file. file should not have any extension.

Adjust the service name in the installSvc.cmd file as described in these steps:
Open the installSvc.cmd file and scroll to the bottom to locate this Comment line:
rem *** Install the service
"%WL_HOME%\server\bin\beasvc" -install -svcname:"Oracle WebLogic %DOMAIN_NAME%_
%SERVER_NAME%" -javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%" -
maxconnectretries:"%MAX_CONNECT_RETRIES%" -host:"%HOST%" -port:"%PORT%" -
extrapath:"%EXTRAPATH%" -password:"%WLS_PW%" -cmdline:%CMDLINE%
Execute your CreateWLSSvc.cmd script as Administrator and check the Windows
Services window
---------------------------------------------
start node manager manually
cmd run as admin->cd <weblogic_server_install_location>\user_projects\domains\
<domain_name>\bin(path) startnodemanager.cmd
how to add nodemanager as a windows service
open cmd as admin->copy the path and paste
cd <weblogic_ server_install_location>\user_projects\domains\<domain_name>\bin
installNodeMgrSvc.cmd
start and stop node manager from services when ever required
==================================================
how to install weblogic server->12.1 version
prerequisite->download and install java jdk(java se development kit)1.8
version.download oracle weblogic server installer
extract the weblogic server installer zip file.it will contain a jar file
create a weblogic folder in a required place ex:c:\weblogic
copy the location of jar file
open cmd as admin->cd pathof jar file
java -jar path of jar file/jar filename.jar
installer opened->welcome screen->next->enter location of oracle home->select
weblogic server->install location selected->done
=================================================
ol objects
ubes,media objects,bsfn,views,data structures,appl,table
Object Specifications are stored in specifications tables (F987* series tables) in
Central Objects data source.
Some objects contain C components (e.g *.c, *.h, *.obj, etc) which are stored
centrally on the deployment server directories.
non ol objects
menus,workflow objects,udc,dd items,tasks, task relationships,rd,bssv property
------------------------------------------------
pkg build(include,source,bin,spec(spec.ini),lib,res,checkin,serverlogs-
>(text,compilelog,generateNER log,svrpkgbuild.log),package_inf)
The purpose of a package is to group software modifications so that they can be
deployed to enterprise servers, web servers, and workstations.
A package can contain everything that is needed to run the software (as in an
initial installation for a new workstation), or
only updates or changes to existing applications.
types
full client
includes full set of specs,bsfn dlls,source files,object files,header
files,bitmaps,inf file.
A full package contains everything that developers need to run in order to develop
in JD Edwards EnterpriseOne software
INF file defines the components that are included in the package, the source and
destination paths for those components,
and the attributes that are needed to install the package.
used for initial installations.
full server::
same as client except below points:
don't include client specific bsfns,features. specs will be stored in database
datasource.
update client
enables you to update, add to, or refresh the existing full package with changed
objects.
update server
Update server packages include only the objects that were described previously for
full server packages.
The maximum length for a package name is eight characters
W-refers web
assesmble(p9601,p9601W)->pkg name,pathcode,type of pkg, if update pkg parent
pkg,pkg description next form->objects,langugage,foundation etc.

define(p9621)->build options,build spec opt,bsfn build opt,compress opt,build

feature opt,type of pkg(client,server)
build->submit pkg for build
If ES is running in 32 bit system, then server only pkg must be on 32bit system. if
ES is 64 then pkg must be on 64.
client pkg runs on 32/64 bit system using multifoundation without considering the
bitness of ES.
bitness of ES and Dep server no need to match if multifoundation is selected during
foundation in pkg assembly.
when building a pkg for first time with 64 bit system, a process is started to
convert source and include files from repository to 64bit,source64,include64.
It inserts the include, source,include64, and source64 files into the
repository.This happens only once.when a package is built, the package contains
both
include, source, include64, and source64 files in the package.
If the client foundation is 32-bit, then it uses the include and source to build
bin32 and lib32 files with the include64 and source64 files existing in the
package.
If the client foundation is 64-bit, then it uses the include64 and source64 files
to build bin64 and lib64 files with the include and source files existing in the
package.
If ES-32 bit uses checkin/include,checkin/source to build bin32 and lib32 with
checkin/include64,checkin/source64 existing in pkg.
if ES-64 bit uses checkin/include64,checkin/source64 to build bin64 and lib64 with
checkin/include,checkin/source existing in pkg.
During the client install, the include,source, include64, and source64 are
delivered with the client package.
During the deploy of the Enterprise Server, only the bin32 or bin64 are deployed.
deploy(p9631)->deploy the pkg to required servers.

from web:
a new service (jde B9 client network service) should be added to deployment server.
we can control(start/stop) this service from sm
this service access accepts message from ES and starts client pkg build.to deploy a
client pkg from web this service must be in running state.
if service is down client pkg build will fail since it is not communicating with
dep server.
server pkg build will be successful if service is down. without connecting to dep
server, pkg finishes in ES.
When you run a server or a client package from the web, the port number of the
enterprise server that the web is accessing must match the port number of the
deployment server in jde.ini.
To change the port number on the deployment server, access the Server Manager and
select the deployment server instance.
You must stop the services,change the port number in jde.ini, and restart the
service to enable the web package to access the deployment server.'

from web:
p9601w->add pkg by clicking on add->row menu->select language,features,foundation
for update pkg we can also add objects from row menu
to activate pkg select define build from row menu

why all kernels will be locked during deployment?

if kernels are locked then ubes will not submit.

server package:
server pkg is a group of specs records,source files,header files and compiled
objecs created on ES.
server pkg is same as client except:
foundation will not be deployed, few bsfns will not be deployed(client only
bsfns),specs are built directly in specified specs datasources,
specs are copied from central objects to database pkg tables.

spec.ini file is required to retrive pkg and spec data source information. spec.ini
will be created by pkg build

directory structure for dep server:

pathcode(DV920/PY920/PD920)\pkg\pkg name
for 32 bit
include,source,bin64,lib32,java,obj,res,serverlogs,spec,work
for 64 bit
include,include64,source,source64,bin64,lib32,java,obj,res,serverlogs,spec,work

directory structure for enterprise server:

pathcode(DV920/PY920/PD920)\pkg\pkg name
bin 32/64,lib
32/64,source,include,checkin/include,checkin/include64,checkin/source,checkin/
source64,compilelogs,generateNerlog,compress,text,res,work,spec,obj
bsfn errors can be find buildlog under work directory.
bssv log->pkg\pkgname\work\sbf
=======================================================================
fundamental elements of cnc architechture:
objects,objects storage,object deployment,environments,pathcode,datasources,ocm
------------------------------------------------------------------
middleware-middleware is a layer between os and business applications.
3 types of middleware-jdenet,jdb,oracle fusion
jdenet->provides communication between client-server,server-server and sends
messages for requests.
jdb->provides client-server,server-server database access by using dynamic sql
queries. provides platform-independent APIs for multiple database access.
------------------------------------
pathcode creation:
create new directory on dep server.copy subdirectories.create database.create a new
table schema.modify ol-status detail table and version list table with new
pathcode.
copy specs from old pathcode to new. create new data source.p00942->modify pathcode
definition.copy pkgs from existing to new pathcode and modify package_inf file.
create new environment.modify ocm mappings for new env.
----------------------------------------------------------------
datasource
it is a collection of tables and how we find and locate those tables.
defines where data is stored and logic is processed.
database datasource->points to location of data.
logic datasource->points the machine where logic is executed/processed.
creating a datasource:
P986115->select databse or logic datasource.click on add
dstasourcename,ds use,type,class,platform,servername,owner id,db name.click ok.
to modify ds:
P986115->select the dtasource to be modified.datasource revisionform will be opened
complete or modify required fileds.click ok.
----------------------------------------------
environment creation
location of env definitions->F0093,F0094,F00941,F00942,F986101
using director mode:
p989400->on copy env/pkgs, select create/copy to new env option.next.select copy
env.enter existing env name in existing env field.next.select director option.next
for env properties,enter env name,dexription,prefix,release.next.verify
pathoce.next.verify the selected enterprise server.next.
on db script generator select windows.select database type.next.select load
business data and load control tables.next.
click ok.revisions form verify data.click cancel and click yes.close env copy form.
2nd method:
p0094->work with env->find->select env.select copy env from row exit.enter new env
and check copy public records only.click ok and click close.
work with env form.in detail area highlight new env and select .enter env
name,description,pathcode,release,developer(Y/N),justintime install(JITI).click ok
and close.

creating only env not pathcode

Log into the deployment server, into the JDEPLAN environment
Copy an existing environment
Create the Business Data and Control Tables Data Sources (DS’s) (if you’re only
creating a new environment and not a new pathcode with it)
NOTE: This requires a new DB to be created to hold the tables for these DS’s as
well as copying over those tables into the new DS’s.
Update OCMs – change original Business Data and Control Tables mappings to the new
Data Sources that were created for this environment
Log into a fat client and repeat steps 2 – 4
Create new Business Data and Control Tables Data Sources in Server Map
Copy OCMs from System to Server Map using R98611A, which calls R986121
Create a new JAS instance for the new environment

===============================================================
client server full pkg build:
F98780R-repository table
F98780T-repository history table
client:
server pkg ube(R9621S) initiates server pkg build.system creates pkg build
directories on deployment machine.
system check for F00942T->emdbsrcflag=1. if value is 0 or blank,objects will not be
inserted into repository table.
system check for F00942T->emenvfu2=1. if value is 0 or blank, include and source
files have not been converted to 64 bit
if F00942T->emdbsrcflag=0 or F00942T->emenvfu2=0,system sets emdbsrcflag=2 for
processing.it does a fetch from f9860 for all objects excpet the one which are
having system code as 88.
if foundation selected for pkg is 32 bit, then bsfns,par files,tables will include
source and incldue files.sets F00942T->emdbsrc=1 and enenvfu2=0
if foundation is 64 bit, converts include and source to 64 bit files and 4
directories will be created.sets f00942t->emdbsrc=1 and emenvfu2=1
system initiates the connection to enterprise primary server.
ES:
creates directories on primary ES and builds the list of objects from F96225(pkg
build history table).
system will check the specs in live specs tables and if specs are not there, it
will get from central objects pathcode and insert them into Live specs table
F98710,711,712,713.
if f00942t->emdbsrcflg=1, get objects from F9860 and put the files in checkin\
source,checkin\include,and bitmaps in checkin\res directories on primary ES.
if f00942t->emdbsrcflg=0,transfers bsfn .c,.h files from checkin location of dep
server to primary ES directories.
compresses chckin\res in dep server and transfers res.cab to checkin\res in primary
ES.
Primary ES will connect with other ES to start the build process.
Moves server only .c and .h files to include and source directories in primary ES.
complies bsfns on primary ES.primary es will communicate to other es to start bsfn
build.
Build specs on primary ES and results will be stored in pkg specs tables.
if client pkg is selected, primary es transfers files from
checkin/include/source/res to include,source,res on dep server.
if client pkg is selected,res.cab is transfered to dep server res directory. client
then uncompresses the res directory.
client:
sends message to primary ES to check the status
ES:
if compress feature is enabled, primary es will send a message to compress for
other ES.transfers compressed file and compress.inf file to dep server pkg
directory
check jde.ini to create the jar file. if field is Y then creates a jar file under
pkg name.
transfer serverlog to dep server under pkg name server logs directory.
transfers files under text directory to dep server pkg name\serverlogs\text
transfers compile logs directory to dep server pkg name\serverlogs\servername
transfers generateNERlogs from primary ES to dep server pkg name
server pkg is completed.
client:
runs client pkg R9622c ube to start client pkg build.
create pkg inf file
compress .c,.ch files using busbuild.
creates specs.ini
if f00924t->emdbsrc-1 or 3 then get sbf files from repository table.if value is 0
copy from pathcode\sbf directory.build bssv.
waits for compile of bsfns,buildng of specs,building of bssv to complete.
copies the generated NER .c,.h files back to checkin location
compress the directories on dep server is compression is selected.
client pkg is completed. pkg is ready to deploy
====================================================================
Full pkg deployment:
set f9651 field will be 50 to prepare the server to deploy.jas server applies lock
on web application
set f9651 field to 10 to indicate deployment is in progress
es will send message to kernels to lock to prevent any ube being submitted.
process waits until ube gets completed. it will wait based on time mentioned in
jde.ini delpoywaitinmin. if time is exceed locks will be released abd deployment
will not happen.
deletes ddict,ddtxt,glbtbl specs from pathcode/spec folder.
clear runtime cache from patcode runtime cache folder.
release kernel locks'=
sets f9651 field as 30 to indicate deployment is finished.
update the record in F96511 with ES information,port number, pathcode,pkg name,type
30 to indicate this is a deployed pkg
if pkg is client pkg update the record in F98225

F98306 - Processing Option Text