I was triggered by the article of Uma Prabhala on Steven Chan's weblog, called Ten Ways of Using iSetup to Streamline E-Business Suite Implementations. To be honest, I thought that iSetup was decommisioned (see the message on https://isetup.oracle.com), but it appears that it is still alive and in fact it looks more promising then ever. When I tried to do the setup I encountered an issue on creating a .dbc file, which is a mandatory setup step.

Although the user manual is not so clear about it, I learned pretty soon that .dbc stands for a database connection file. This file usually needs to be created by a DBA. A template file is available in $FND_TOP/secure, and needs to be renamed and slightly altered. See the code below, I highlighted the parts I changed.

After the .dbc file is created on the server, enter the DBC Filename. The database connection will be used to select the next field, Responsibility name.

# $Header: template.dbc 120.0 2005/05/07 16:45:30 appldev ship $
# TEMPLATE.dbc
# Template database configuration file.
#
# Create one copy of this file for each database instance this
# Applications Server will connect to. Each file should have the name
# .dbc
# and be located in this directory ($FND_TOP/secure).
# Change each of the parameters below to values appropriate for
# the database instance. Do not change the syntax.
#
# This file can be gererated using the AdminAppServer tool.
# This is a java utility that can be run from the command line.
# Instructions to use this tool are documented in the Applications
# Sysadmin Manual.

#
# TWO_TASK
# SQL*Net name of database.
#
TWO_TASK=database

#
# FNDNAM
# Oracle User to be used for Oracle Applications connection.
# The FNDNAM Oracle User must have Oracle Applications privilege level
# 'Universal'.
#
FNDNAM=APPS

#
# GWYUID
# Oracle User/Password of the public account to be used for initial
# Oracle Applications connection.
# The GWYUID Oracle User must have Oracle Applications privilege level
# 'Public'.
#
GWYUID=APPLSYSPUB/PUB

#
# GUEST_USER_PWD
# Applications User/Password of the Guest user.
# The Guest Applications User is a public Applications user
# with no responsibilities assigned. If no such user exists,
# create one in the 'Define User' form. Do not use a user with
# any active responsibilities. Note: This parameter is for
# an applications user NOT an Oracle user. The Guest user
# is seeded with 11i.

GUEST_USER_PWD=GUEST/GUEST

# THE FOLLOWING PARAMETERS ARE RELEVANT ONLY
# IF JDBC IS BEING USED. IF THEY ARE NOT SUPPLIED, DEFAULTS
# WILL BE USED.

# APPS_JDBC_DRIVER_TYPE
# The type of JDBC driver being used. If no value is supplied,
# the thick (OCI) driver will be used. Give a value of THIN
# or THICK depending on the type of JDBC driver to be used.
# For a detailed discussion on the THIN vs the THICK driver,
# refer to the JDBC documentation. For Release 11i , this
# should be set to a value of THIN.


APPS_JDBC_DRIVER_TYPE=THIN

# DB_HOST
# The host machine on which the database resides. This parameter
# is required only if the THIN DRIVER is being used.

DB_HOST=host_name

# DB_PORT
# The port of the host machine on which the database resides.
# This is required only if the THIN driver is being used.

DB_PORT=port_number

# DB_NAME
# Database instance name.
# This is required only if the THIN driver is being used.
# If no value is provided, the TWO_TASK is used.

# DB_NAME=db_name

TweetShare

Comments

nhawi

0

 

 

Dear Sir,
I'm try to use iSetup to extract BG but I have an error as follow
An error occurred in API 'Operating Units API'
View Object 'ClassificationTypeVO'
please adivice

thanks

Monday 23 March 2009, 00:27

Please login to post comments or replies.