Skip to main content
Skip table of contents

JD Edwards Objects and Configuration

You must deploy the required Cantara custom objects before the Cantara Access Server can fully interact with your JD Edwards server. The objects are provided as an Object Management Workbench (OMW) archive file.

Refer to your JD Edwards documentation for details about how to create, manage and deploy projects using your JD Edwards development client.

Creating the OMW Project

  1. Create a new project in OMW to contain the Cantara JD Edwards objects.
  2. Select the project and click on the Restore icon at the bottom of the OMW action icons.
  3. When prompted, click Yes to use a ZIP file.
  4. Browse to the PRJ_CNTR_BASE_E9x0_4.2.x.par file provided.
  5. Click the Open button to extract the archive and create the necessary objects within the OMW projects.
  6. Once the build is complete it is important to generate the new tables that are included in the project.

Repeat the same process for the services objects which will be in a files named PRJ_CNTR_GRP_E9x0_4.2.x.par.

Deploying the Objects

Once you have created the project you can now go through the normal process of building and deploying new objects within your JD Edwards environment. 

Deployment Required

You must deploy all of the provided objects to each JD Edwards Logic or Batch server that you wish to connect to prior to defining the connection in the Cantara Administration Console.

Special Instructions

For new installations the only additional tasks to be completed is to generate any tables included in the OMW projects. For the base components the following tables must be generated:

  1. FQ35CA01
  2. FQ35CA10
  3. FQ35CA11

JDE.INI Settings

To ensure correct operation of all of the Cantara features the following jde.ini file settings should be confirmed.

  1. Ensure that sufficient processes are available for the XML List Kernel

    JDENET_KERNEL_DEF16

    TEXT
    [JDENET_KERNEL_DEF16]
    krnlName=XML List Kernel
    dispatchDLLName=xmllist.dll
    dispatchDLLFunction=_XMLListDispatch@28
    maxNumberOfProcesses=3
    numberOfAutoStartProcesses=1
  2. Ensure that sufficient processes are available for the XML Dispatch Kernel

    JDENET_KERNEL_DEF22

    TEXT
    [JDENET_KERNEL_DEF22]
    krnlName=XML DISPATCH KERNEL
    dispatchDLLName=xmldispatch.dll
    dispatchDLLFunction=_XMLDispatch@28
    maxNumberOfProcesses=3
    numberOfAutoStartProcesses=1
  3. Ensure that the LREngine has a suitable output storage location and sufficient disk allocation

    LREngine

    TEXT
    [LREngine]
    System=C:\JDEdwardsPPack\E920\output
    Repository_Size=20
    Disk_Monitor=YES
  4. Ensure that the XML Kernels are correctly defined

    XMLLookupInfo

    TEXT
    [XMLLookupInfo]
    XMLRequestType1=list
    XMLKernelMessageRange1=5257
    XMLKernelHostName1=local
    XMLKernelPort1=0
     
    XMLRequestType2=callmethod
    XMLKernelMessageRange2=920
    XMLKernelHostName2=local
    XMLKernelPort2=0
     
    XMLRequestType3=trans
    XMLKernelMessageRange3=5001
    XMLKernelHostName3=local
    XMLKernelPort3=0
     
    XMLRequestType4=JDEMSGWFINTEROP
    XMLKernelMessageRange4=4003
    XMLKernelHostName4=local
    XMLKernelPort4=0
    XMLKernelReply4=0
     
    XMLRequestType5=xapicallmethod
    XMLKernelMessageRange5=14251
    XMLKernelHostName5=local
    XMLKernelPort5=0
    XMLKernelReply5=0
     
    XMLRequestType6=realTimeEvent
    XMLKernelMessageRange6=14251
    XMLKernelHostName6=local
    XMLKernelPort6=0
    XMLKernelReply6=0
     
    XMLRequestType7=ube
    XMLKernelHostName7=local
    XMLKernelMessageRange7=380
    XMLKernelPort7=0
    XMLKernelReply7=1

 

 

 

On This Page

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.