Oracle Utilities Software Development Kit V2.2.0 Installation Guide
Oracle Utilities Software Development Kit V2.2.0 Installation Guide
PROPRIETARY INFORMATION
THIS MATERIAL CONTAINS, AND IS PART OF, A COMPUTER SOFTWARE APPLICATION
WHICH IS PROPRIETARY INFORMATION OWNED BY ORACLE CORPORATION. THE
APPLICATION, INCLUDING THIS MATERIAL, MAY NOT BE DUPLICATED, DISCLOSED OR
REPRODUCED IN WHOLE OR IN PART FOR ANY PURPOSE WITHOUT THE EXPRESS
WRITTEN AUTHORIZATION OF ORACLE CORPORATION.
This Document is subject to change without notice, and Oracle Corporation does not warrant that
the material contained in this Document is error-free. If you find any problems with this
Document, please report them to Oracle Corporation in writing.
Oracle Corporation and Oracle are registered trademarks of Oracle Corporation or one of its
subsidiaries. All other products or company names mentioned are used for identification
purposes only, and may be trademarks of their respective owners.
Table of Contents
Table of Contents .......................................................................................................................... 3
Contents
Known Issues
Components Of The Oracle Utilities Software Development Kit
Setting Up For Development
Appendix
Known Issues
Development Project
Workstation Repository
Sync / Submit Code
Sy
st
em
D
at
a
Project
Dev DB
Development Environment
Development
Client
The following are both Development
Clients:
• Project Repository
• Development Workstation
Development Client
Contents
Project Development Database
Project Repository
Development Workstation
Project Repository
The project repository serves the following purposes:
It is the central storage for all completed, unit-tested code.
It provides the environment from which to build the latest state of the project.
It provides the latest state of the project dev app server from which all developers can
synchronize with.
It is the source for CM Packaging.
To support these purposes:
It has to be accessible to all developers.
It is set up as a development client, i.e., similar to a development workstation (see
Development Workstation below).
Development Workstation
Developers write, generate, compile, and test code on development workstations. A
development client is installed for each project that the developer works on.
The main components of a development client are the following:
Project Dev App Server. Code is developed on and executables built into the project dev
app server.
Oracle Utilities Software Development Kit Client. This is the primary development tool of the
Oracle Utilities Software Development Kit and contains COBOL development tools.
Eclipse SDK. This is the Java development tool used in the Oracle Utilities Software
Development Kit.
Contents
Setting Up the Project Development Database
Setting Up the Project Repository
Setting Up Development Workstations
Setting Up For CM Packaging
Setting Up A Build Server
Pre-Requisites
The project repository requires additional software because it is a development environment.
Contents
Microsoft .NET Framework Version 3.5 Redistributable Package
Install and Configure NetExpress
Note. Micro Focus Net Express is required only if there will be code developed in COBOL.
Note. Micro Focus Application Server must first be uninstalled before installing Micro Focus Net
Express.
You must purchase and install the Micro Focus Net Express product and apply the appropriate
wrappack.
Please refer to the supported platforms document for the appropriate version of NetExpress.
Ensure that the system path for the development workstation includes the NetExpress\Base\bin
as part of the PATH.
Note. Development workstations must install this software in the same drive and directory in their
development workstations. It is important that the installation directory be chosen carefully so
that this be achieved.
Setup
The following are the steps in creating a project repository:
Install an app server.
Install an Oracle Utilities Software Development Kit Client or configure the app server for
development.
Note. Installing the Oracle Utilities Software Development Kit Client also configures the app
server it is set up with to be a development app server. If the Oracle Utilities Software
Development Kit Client was installed in the previous step, its installation already configured the
app server for development and there is no need to execute this step.
Note. Since the project repository is a development environment, developers just synchronize
the project repository's development app server into their development workstations using a
source code control system instead of installing and building one for themselves. However, this
means that the drive names and directories must be the same in the project repository and in the
development workstations.
Contents
Install Oracle Utilities Software Development Kit Client
Configure App Server for Development
Note. It is important to first switch to a project with the required version of the Oracle Utilities
Software Development Kit because the process of configuring an app server for development
uses the current project's version of the Oracle Utilities Software Development Kit to configure it.
Open the Oracle Utilities Software Development Kit Client Scripts folder by going through
Start Programs Oracle Utilities Software Development Kit 2.2.0.x Oracle Utilities
Software Development Kit Client Scripts; x denotes the build number.
Double-click on createNewEnv.bat to initiate configuration of an app server for development.
Specify the directory of the app server to configure for development upon being prompted.
The script displays messages describing what was done to configure the app server for
development and then asks the user to press any key when done.
Note. The user must execute switchEnvironments.bat and select the newly-configured project to
begin working that project.
Note. When the project needs to be deployed locally, the developer has to change the
environment variables in the “environ.ini” in the “etc” folder of the application server.
e.g. C:\spl\V220_CCB_SDK_WIN_ORA_TCAT\etc\ ENVIRON.INI
The variables BSN_WLHOST, WEB_WLHOST must be changed to point to the “localhost”.
Contents
Pre-Requisites
Setup
Synchronize to Project Repository Dev App Server
Setting up the Oracle Utilities Software Development Kit Client
Install Eclipse SDK
Online Help
Pre-Requisites
Contents
Recommended Hardware Configuration
Microsoft Windows XP
Pre-Requisites of the Product to be Customized
Microsoft .NET Framework Version 3.5 Redistributable Package
Microsoft Windows XP
Please refer to the supported platforms document for the appropriate version of the windows
client
Setup
The following are the steps in creating a development client:
Synchronize to the development app server from the project repository.
Install an Oracle Utilities Software Development Kit Client or configure the app server for
development.
Note. Installing the Oracle Utilities Software Development Kit Client also configures the app
server it is set up with to be a development app server. If the Oracle Utilities Software
Development Kit Client was installed in the previous step, its installation already configured the
app server for development and there is no need to execute this step.
Note. Since the project repository is a development environment, developers just synchronize a
copy of the project repository's development app server into their development workstations
instead of installing and building one for themselves. However, this means that the drive names
and directories must be the same in the project repository and in the development workstations.
Note. The project repository can simply be a shadow/replica from a source code control system,
in which case, the developer just checks in the code and the project repository is automatically
updated.
Note. The project repository development app server must be synchronized to the development
workstation to the exact same drive letter and directory.
Note. If Perforce is used to synchronize the project repository, then It checks-out the files in
read-only mode. Make sure that these synchronized folders are writeable.
Note. The project repository and all dev workstations must use the same Oracle Utilities
Software Development Kit Client version.
Online Help
Online Help is available in the Help menu of the Oracle Utilities Application Workbench.
The online help can also be accessed through the MS Windows Start menu or by entering the
path directly on the web browser.
Using the MS Windows Start menu, do the following menu selections:
Start All Programs Oracle Utilities Software Development Kit 2.2.0.x Oracle Utilities
Software Development Kit Help, here x denotes the build number.
Using a web browser, enter the following path in the address bar of the web browser:
file:///<splsdkroot>/SDK/2.2.0.x/help/ENG/SPLHelp.html
Contents
Database CM Packaging Tool
App Server CM Packaging Tool
Appendix
Contents
Installing the Oracle Utilities Software Development Kit Client
Installing the Eclipse SDK for the Project Repository
Installing the Eclipse SDK for Developers
Note. It is necessary to have the Windows regional settings changed to English (USA) before
installing the Oracle Utilities Software Development Kit
Click Next.
Enter the directory name to install the Oracle Utilities Software Development Kit into. An
environment variable called SPLSDKROOT will be set to this value. Note that if the
SPLSDKROOT has been set by a previous install, this value must not be changed so that both
new and old versions of the Oracle Utilities Software Development Kit will function seamlessly. If
the value has been previously set, it is indicated in the dialog box. Click Next to continue.
Note. Do not use the same directory where app servers are installed because the Oracle Utilities
Software Development Kit creates directories that may conflict with the app servers.
Select the location of the runtime application server that you want to use for development and
click Next to continue.
Enter the location to the installed Java runtime environment and click Next.
The database information is defaulted to information that the runtime application server is using.
Only the DB schema is not obtained from server. Update the information as necessary and click
Next to continue.
Contents
Initial Eclipse Setup
Configuring Eclipse Project via Oracle Utilities Eclipse Configuration
Configuring Eclipse Project manually
Set Up To Run Artifact Generator
Set Up to Deploy cm.jar
Note. This step only needs to be done once per version of the SDK.
Launch Eclipse
Start Eclipse by opening the Oracle Utilities Software Development Kit Client Scripts directory
(Start All Programs Oracle Utilities Software Development Kit 2.2.0.x Oracle Utilities
Software Development Kit Client Scripts) and then double-clicking startEclipse.bat; x is the
build number.
This launches Eclipse with the Welcome tab shown.
Select the app server directory and click OK on the Folder selection window.
The Preferences window shows the asBase variable that was created.
Overview
Once the base Eclipse setup is done and the application server base is set as a linked resource,
it is the time to setup a project and setup the classpath. The Oracle Utilities Eclipse Configuration
setup is an easy way to configure classpath and other configurations.
Note. Oracle Utilities Eclipse Configuration configures a project with name “EclipseProject220”.
If one chooses not to use this, a manual setup and configuration of eclipse is also available.
Pre-requisites
This installation assumes that the environment already has the Application Server and
Eclipse already installed.
Eclipse must be configured to have the link resource (asBase) for the Application Server.
Install configuration
Following steps will install the eclipse configuration.
Close all Eclipse instances. Double click on the UtilitiesEclipseConfig.exe to get started.
Press Next.
Select the program group for the installation and press Next.
Once the installation is finished, the program group appears in the Windows Start -> Programs -
> Oracle Utilities Eclipse Config 2.2.0.
Once the installation is done, SPLSDKCommon folder under the Application Server can be
checked for the following folders and files.
If the application server is installed under C:\spl\V220_CCB_SDK_WIN_ORA_TCAT, then
the C:\SPL\V220_CCB_SDK_BLD13_WIN_ORA_TCAT\SPLSDKCommon folder contains
the following folders and files.
The folder
C:\spl\V220_CCB_SDK_WIN_ORA_TCAT\SPLSDKCommon\eclipseLaunchScripts
contains following files:
Note. The Oracle Utilities Eclipse Configuration DOES NOT install another Eclipse. It sets
classpaths to reduce the manual configuration.
Once the eclipse is open, right click on the Package Explorer, Click on Import. Select
General/Existing Projects into Workspace and press Next.
Select the Root Directory as the eclipseProject from the application server.
Eclipse wizard shows the “EclipseProject220” in the Projects. Accept the default selection
and click Finish.
Once the project is imported it would automatically sets all the class paths and build paths.
This current configuration is ready to work.
Select the SPLSDKCommon\eclipseProject directory of the app server and click OK.
Click Finish.
Contents
Set Up Non-Source Folders
Set Up tools Folder
Set Up lib Folder
Set Up cobol Folder
Set Up target Folder
Set Up xmlMetaInfo Folder
Set Up launchScripts Folder
Set Up Eclipse Build Path
Set Default Output Folder
Add Sources
Add Libraries
Finish Setting Up Build Path
Add Sources
Contents
Remove Project Folder as Source Folder
Add java Folder
Add gen Folder
Add Libraries
Launch the project properties window, select Java Build Path and then the Libraries tab.
Contents
Add jars from lib
Add jars from tools
Finish Adding Libraries
Click OK. The selected jar files show up in the Libraries tab.
Once the Properties window appears, select the “SPL Database Proeprties” and fill appropriatly.
Note. This is a necessary step before any of the SPL Eclipse Wizards are used. (e.g.
Maintenance Wizard Implementation Class, Batch Job, Algorithm Implementation, etc…)
Note. The artifact generator cannot complete successfully unless there is some Java code.
If Oracle Utilities Eclipse Configuration is used for Eclipse setup, please follow Configuration after
Oracle Utilities Eclipse Configuration setup. Otherwise please follow Configuration after Manual
EclipseSetup.
Contents
Configuration after Oracle Utilities Eclipse Configuration setup
Configuration after Manual Eclipse Setup
Press Add.
Select Java Application and click on the New launch configuration icon.
Contents
Main Tab
Arguments Tab
Main Tab
Specify a name. For example, Generate Artifacts.
Specify the main class as
com.splwg.tools.artifactgen.ArtifactGenerator
Arguments Tab
Specify the following as class arguments, substituting appropriate values to text bound by '<'
and '>':
-deleteAll
-appJars
${resource_loc:/<projectName>/lib/spl-base-<version>.jar}
${resource_loc:/<projectName>/lib/spl-<product>-<version>.jar}
-extraSvcMetaDirs
${resource_loc:/<projectName>/xmlMetaInfo}
Note. Make sure there is a space before all dash ('-') and dollar ('$') characters.
-Dspl.tools.artifact.manual.sourcedir=${resource_loc:/<projectName>/java}
-Dspl.tools.artifact.generated.sourcedir=${resource_loc:/<projectName>/gen}
-Dspl.tools.artifact.cobol.sourcedir=${resource_loc:/<projectName>/cobol}
-Dspl.tools.loaded.applications=base,<product>,cm
Select Run from the Display in favorites menu section and click Apply, then Close.
The Package Explorer shows the Generate Artifacts.launch script under the launchScripts
folder.
Once the favorite is added, it appears on the Run External Tools menu.
Click on the Run External Tools Menu and then the “External Tools…”
Select the Ant Build -> EclipseProject220_Deploy and select the Properties tab and uncheck
the “Use Global Properties as specified in the Ant Runtime preferences”. Now add a new
property as “asBase” if the property does not exist. Verify the value is set to the app server
directory.
Now Apply the changes and click Run External Tools -> EclipseProject220_Deploy to
deploy the cm.jar. Following is the console output once cm.jar is successfully deployed.
Expand the tools folder from the package explorer and deploy.xml is shown.
Right click on deploy.xml, select Run as, then select 2 Ant Build...
Click on the Add Property button. The Add Property window appears.
Specify asBase as the property name and the app server directory as the value and click
OK.
The Package Explorer shows the deploy launch script under the launchScripts folder and
the Console shows a successful build.
The same command is available at Run -> Run External Tools -> Deploy menu
Note. This step only needs to be done once per version of the SDK.
Launch Eclipse
Start Eclipse by opening the Oracle Utilities Software Development Kit Client Scripts directory
(Start All Programs Oracle Utilities Software Development Kit 2.2.0.x Oracle Utilities
Software Development Kit Client Scripts) and then double-clicking startEclipse.cmd, x is the
build number.
This launches Eclipse with the Welcome tab shown.
Select the app server directory and click OK on the Folder selection and New Variable
windows.
The Preferences window shows the asBase variable that was created. Click OK to close the
window.
Select the eclipseProject folder in the Client folder and click Ok.
The project is shown as it was set up in the project repository. Select the project and click
Finish.