|
| HOW TO REPLACE THE LOGOS IN ORACLE APPLICATIONS Rel 11i !!!!! |
| Friday, October 30, 2009 |
There are 4 main logos screens in the signon process of Rel 11i
Initial Screen (with Jinitiator Download notice)
Splash Screen
FNDSCSGN (Applictaions Signon Screen)
ICXINDEX.htm (Self Service Signon Screen)
Changing the images that appear when signing on to Oracle Applications R11i
is a customization of that form. Applications sign-on form FNDSCSGN contains
a procedure called START_UP that uses a built-in READ_IMAGE_FILE to call the
logo image file from the operating system at the runtime.
The signon Form uses both the JAR files and files stored on the file system.
Applying any patches that modifies JAR files can revert to the default logo and
must be modified each time, and is therefore NOT supported.
However, this may offer some guidelines for how I did it
I. First when you call the dynamic html page from the Rel 11i Portal Page
http://machine_name:port_number/dev60cgi/f60cgi
This logo.gif file can be found and replaced in the directory
$OA_MEDIA/logo.gif
II. Next a Splash screen pops up while the jar files are loading and then goes
away. This screen picture is called splash.gif.
(looks like a purple/blue color and says WEB DEVELOPER and has a hammer)
can be changed in FORMS60/java/oracle/forms/icons/splash.gif
This Web Developer logo appears as a splash screen on Applications 11i Startup. This is due to the missing Apps logo in 11i. The original fix was to copy the
Appslogo.gif (or your company logo) over the Developer logo
FORMS60/java/oracle/forms/icons/splash.gif .
The new fix (rerelease of 11iRI) is to ADD the Appslogo.gif (or your company logo) into $FND_TOP/media/splash.gif from where it can be AD copied (or manually
copied) to $JAVA_TOP/oracle/apps/media/
Next, we need to point to it in $OA_HTML/bin/appsweb.cfg by adding the PATH
to the splashScreen= line of appsweb.cfg .
like this....
splashScreen=oracle/apps/media/splash.gif
This will be fixed in the appsweb.cfg of Rapid Installer for 11.5.2 according to BUG 1355330
III. $FNDTOP/media/logo.gif is where you change for the Self Service signon screen Remember that you will need to bounce the WebDB 2.5 listener once a change is made.
IV. Changing the actual FNDSCSGN SignOn screen, which is an Oracle Form.
there are two logo/pictures in this window.
The SignOn screen FNDSCSGN references a *.gif file called logo.gif and tries to get it from the JAR file FNDAOL.jar, if it doesn't find it then it looks for it on the file system, so you need to replace logo.gif in both places.
Oracle/prodcomn/java/oracle/apps/media/logo.gif
Oracle/prodcomn/java/oracle/apps/media/appslogo.gif
Oracle/prodappl/fnd/11.5.0/java/jar/fndaol.jar
You can use WinZip to open FNDAOL.jar and replace (delete then add) the logo.gif file.
Remember to clear your Client PC's browser cache and delete all the files in jcache
c:\Program Files\oracle\Jinitiator11727\jcache\*.*
to download the new jar files and the changes that you made.
OTHER NOTES ON THIS TOPIC
-------------------------
Note 421636.1 - How to replace the default Oracle Logo with a Customized Logo? |
posted by Jaswinder Singh @ 6:59 AM   |
|
|
|
| Changing the ODS schema password in OAS !!!!! |
| Monday, September 7, 2009 |
OID Database Schema Owner
The Oracle Internet Directory runs on an Oracle database and creates two database users: ODS and ODSCOMMON. ODS is the schema owner that contains all of the database objects (tables, views, objects, etc.) used for OID functionality and directory storage. When the OID needs to login to the database, it uses the ODS database account which has a default password of ODS. You should secure this database user account before putting the LDAP directory into production.
1. Change the ODS password to the desired value, and create the new wallet:
oidpasswd connect= change_oiddb_pwd=true
oidpasswd connect= create_wallet=true
2. Restart OID:
opmnctl stopproc process-type=OID
opmnctl status
opmnctl startproc process-type=OID
3. Change the password in Enterprise Manager:
1. Login to EM
2. Click Targets tab > Click All Targets tab
3. Find the Name reported in the emagent.trc file (e.g., 10_1_2_portoidd.libby.oracle.com_LDAP) > click on it
4. Click Monitoring Configuration at the bottom right
5. Enter:
Username = ods
Password =
Using the OID Database Password Utility
The DBA can change this password by using the OID Database Password Utility (included with the OID installation). The following example uses this utility to change the database password for ODS:
# $ORACLE_HOME/bin/oidpasswd
current password: ods
new password: new_secret_password
confirm password: new_secret_password
password set.
How oidpasswd Works
The oidpasswd utility connects as the ODSCOMMON user and uses the role ODS_SERVER with the original password to perform the following:
1. Changes the password for the ODS user for the OID schema database.
2. Updates the SYSTEM.ODSINSTANCES table with the new, encrypted password for ODS.
3. Changes the password for the ODS_SERVER role to the new password.
4. Updates the $ORACLE_HOME/ldap/admin/oidpwdr file with the encrypted password.
NOTE: Some Oracle OID patches and scripts may assume the user ODS/ODS. It is advised to change the password for ODS back to its default of ODS during application of patches or when running OID scripts.
But what about ODSCOMMON?
When connecting to the database schema, the OID executables, such as oidctl or oidldapd servers connect as the database user ODSCOMMON. The password for ODSCOMMON is ODSCOMMON, and that password cannot be changed. It is hardcoded in the executables and changing it on the database level will cause an ORA-01017 error. There is no security risk, however, not being able to change the ODSCOMMON password, as it has only CONNECT privilege. Once connected as ODSCOMMON, the executable will obtain the privileges it needs via the role ODS_SERVER, which is protected by the ODS password. The password is obtained by the executable from the SYSTEM.ODSINSTANCES table. This is the password encrypted and set by the oidpasswd utility.
Reference :
Note 316177.1 |
| posted by Jaswinder Singh @ 7:52 PM |
|
|
|
| Find Component Version In Oracle Application Server !!!!!!!!!!!!!! |
| Friday, September 4, 2009 |
Q1. To check the database version?
A. Logon to SQLPLUS as sysdba :
SQL> SELECT * FROM v$version;
BANNER
----------------------------------------------------------------
Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
PL/SQL Release 9.2.0.7.0 - Production
CORE 9.2.0.7.0 Production
TNS for Linux: Version 9.2.0.7.0 - Production
NLSRTL Version 9.2.0.7.0 - Production
Q2. Check the installed component of Oracle Application Server and their Versions.
A. Logon to SQLPLUS as sysdba
SQL> SELECT COMP_NAME,VERSION,STATUS,SCHEMA FROM dba_registry;
COMP_NAME VERSION STATUS SCHEMA
------------------------------ ------------------------------ ----------- ------------------------------
Oracle9i Catalog Views 9.2.0.7.0 VALID SYS
Oracle9i Packages and Types 9.2.0.7.0 VALID SYS
Oracle Workspace Manager 9.2.0.1.0 VALID WMSYS
JServer JAVA Virtual Machine 9.2.0.7.0 VALID SYS
Oracle XDK for Java 9.2.0.9.0 VALID SYS
Oracle9i Java Packages 9.2.0.7.0 VALID SYS
Oracle interMedia 9.2.0.7.0 VALID SYS
Spatial 9.2.0.7.0 VALID MDSYS
Oracle Text 9.2.0.7.0 VALID SYS
Oracle XML Database 9.2.0.7.0 VALID XDB
Oracle Data Mining 9.2.0.7.0 VALID ODM
COMP_NAME VERSION STATUS SCHEMA
------------------------------ ------------------------------ ----------- ------------------------------
OLAP Analytic Workspace 9.2.0.7.0 UPGRADED SYS
Oracle OLAP API 9.2.0.7.0 UPGRADED SYS
OLAP Catalog 9.2.0.7.0 VALID OLAPSYS
14 rows selected.
Q3. How to checkthe Oracle Application Server Version?
A. Login to Mid Tier OS user and check the following :
[mid@oas04 install ~]$ cat $ORACLE_HOME/config/ias.properties | grep Version
Version=9.0.4.2.0
=> also login to database and check the mid tier components:
SQL> select * from ias_versions;
COMPONENT_NAME ID VERSION
-------------------------------------------------- ------------------------------ ------------------------------------------------------------------------------------------
Metadata Repository Container mrc 9.0.4.0.0
Oracle Ultrasearch ultrasearch 9.0.4
Oracle9i workflow workflow 2.6.3
Oracle9iAS Discoverer discoverer 5.1.0.0.0
Oracle9iAS Independent Platform ip 9.0.4.0.0
Oracle9iAS Internet Directory oid OID 9.0.4.0.0
Oracle9iAS Portal portal 9.0.4.3.0
Oracle9iAS Single Sign-On sso 9.0.4.0.99
Oracle9iAS Syndication Server syndication 9.0.4
Oracle9iAS UDDI uddi 9.0.4
Oracle9iAS Wireless wireless 9.0.4.2.0
11 rows selected.
Q4. How to find the Oracle Portal Version?
A. Login to SQLPLUS as portal user or as sysdba:
SQL> select version from portal.wwc_version$;
VERSION
------------------------------------------------------------------------------------------
9.0.4.3.0
Q5. How to detemine the Oracle Single Sign On Version?
A. Login to SQLPLUS as sysdba and check the following query:
SQL> select version from orasso.wwc_version$;
VERSION
------------------------------------------------------------------------------------------
9.0.4.3.0
Q6. To check the Oracle Internet Directory Version?
A. Login to Infra Tier OS user:
[infra@oas04 install]$ $ORACLE_HOME/bin/oidldapd -version
oidldapd: Release 9.0.4.3.0 - Production on Thu Sep 3 21:50:32 2009
(c) Copyright 2001 Oracle Corporation. All rights reserved.
=> At database level :
SQL> select attrval from ods.ds_attrstore where entryid = 1 and attrname = 'orcldirectoryversion';
ATTRVAL
----------------------------------------
OID 9.0.4.3.0
Q7. How do know the Ports?
A. Check the following to know the ports:
[infra@oas04 install]cat $ORACLE_HOME/install/portlist.ini |
| posted by Jaswinder Singh @ 5:15 AM |
|
|
|
| Forms Socket Mode in Oracle Applications Release 12 !!!!!!!!!! |
| Sunday, August 30, 2009 |
Oracle Applications Release12 by default configures Forms 10g stack in servlet mode, as this is the preferred and recommended deployment model for forms on the web.
In this mode a java servlet called the Forms Listener Servlet manages the communication between the Forms Java Client and the OracleAS Forms Services.
The Forms Listener Servlet communicates through the HTTP server port and does not need extra ports to handle the communication between the client and the Oracle Applicaiton Server Forms Services.
The Forms Servlet architecture is also compatible with web applications industry standards and supports different advanced network configurations such as Load balancing effortlesly.
Although Forms Servlet is the preferred deployment method, there may be circumstances where customers need to switch from Forms Servlet mode to Forms Socket mode, which allows desktop clients to access the Forms Server directly. This may be required in the following situations:
==> Disable Forms Socket Mode and re-enable Forms Servlet Mode:
Pre-Checking
=> Check the txkrun.pl script
ls -lrt $FND_TOP/bin/txkrun.pl
-rwxrwxrwx 1 applmgr dba 3673 Jan 3 2007 /test/applmgr/apps/apps_st/appl/fnd/12.0.0/bin/txkrun.pl
=> Navigate to $INST_TOP/appl/admin
grep -i s_frmConnectMode <$TWO_TASK>_HOSTNAME.xml
Expected Result :
socket
1. Bring down the applications instance.
2. Take the cold backup which is recommended.
3. Bring up the Database Tier services.
4. Take Backup of $TWO_TASK_.xml file $INST_TOP/appl/admin/ (On All nodes applicable on multinode installation).
5. Run the following script to disable Forms Socket Mode and re-enable Forms Servlet Mode:
$FND_TOP/bin/txkrun.pl -script=ChangeFormsMode \
-contextfile=$INST_TOP/appl/admin/PTSSAI_.xml \
-mode=servlet \
-runautoconfig=No
Note: Run the above script on Forms Server Nodes only.
6. Run AutoConfig on the application tier (On All nodes applicable on multinode installation):
$INST_TOP/admin/scripts/adautocfg.sh
7. Bring up the mid tier services.
8. Log in to Oracle Applications and launch a Forms-based application.
9. Open the Sun Java Console (from Tools Menu in Internet Explorer).
10. Check whether the "mode" directive displayed in Sun Java Console when launching forms-based applications, is set to http,native
11. Direct Forms Servlet Launch is:
https://hostname:port/forms/frmservlet
References :
Metalink Note : 384241.1 |
| posted by Jaswinder Singh @ 1:17 AM |
|
|
|
| How to Setup Pasta for Epson Esc/P Printers !!!!! |
| Thursday, July 23, 2009 |
1. On server where the concurrent manager resides, setup the printer at the OS level. As the applmgr, verify that the OS print queue is working by submitting a print job, from the OS command line to the target printer, with a simple ASCII text file. Check the OS vendor manual for the command and syntax required or printing from a command line.
i.e lpstat -p
2. If Pasta is not already at the latest version of 3.0.4, install the latest released Pasta patch (3325651). Use the following command to determine the current version of Pasta: FNDPSTAX -v
3. Copy the default Pasta configuration file in order to create a configuration files that support non-Postscript printers (any name can be used *.cfg):
a) cp $FND_TOP/resource/pasta.cfg $FND_TOP/resource/pasta_epson.cfg
b) Take a backup of the pasta_epson.cfg file under $FND_TOP/resource and Edit the pasta_epson.cfg file and change the 'outputFormat' parameter to text and/or a character set that the printer supports, as follows:
i.e. outputFormat=text.WE8ISO8859P1 or outputFormat=text
4. Logon as sysadmin
Responsibility = System Administrator
Navigate --> Install: Printer: Driver
Copy the three main Pasta drivers as following:
==> Copy PASTA_LANDWIDE the PASTA_EPSON_LANDSCAPE
User Driver - Pasta Epson driver for Landscape
Description - Pasta universal driver for Epson Landscape style
SRW Driver - PSTLL
Driver Method - Program
Driver Method Parameters - Check "Spool File" Option
Program Name - FNDPSTAX
Argument - -pn$PROFILES$.PRINTER -f$PROFILES$.FILENAME -c$PROFILES$.CONC_COPIES -l -Fpasta_epson.cfg
Initialization to /eC66/eP/017
==> Copy PASTA_LANDWIDE to PASTA_EPSON_LANDWIDE
User Driver - Pasta Epson driver for Landwide
Description - Pasta universal driver for Epson Landwide style
SRW Driver - PSTWL
Driver Method - Program
Driver Method Parameters - Check "Spool File" Option
Program Name - FNDPSTAX
Argument - -pn$PROFILES$.PRINTER -f$PROFILES$.FILENAME -c$PROFILES$.CONC_COPIES -l -s7 -Fpasta_epson.cfg
Initialization - /eC66/eP/017
==> Copy PASTA_PORTRAIT to PASTA_EPSON__PORTRAIT
User Driver - Pasta Epson driver for Landwide
Description - Pasta universal driver for Epson Portrait style
SRW Driver - PSTWL
Driver Method - Program
Driver Method Parameters - Check "Spool File" Option
Program Name - FNDPSTAX
Argument - -pn$PROFILES$.PRINTER -f$PROFILES$.FILENAME -c$PROFILES$.CONC_COPIES -Fpasta_epson.cfg
Initialization - /eC66/eP
5. Create a new printer type that reuses the existing Pasta print styles. Link the styles to the new Pasta printer drivers for Epson Esc/P (non-Postscript) printers.
a) Responsibility = System Administrator
b) Navigate --> Install: Printer: Types
c) Create a new printer type such as
Type: Pasta Epson Printer Type
Description : Pasta Epson Printer Type
Style Driver
Landscape PASTA_EPSON_LANDSCAPE
Landwide PASTA_EPSON_LANDWIDE
Portrait PASTA_EPSON__PORTRAIT
6. On the Apps register printer form, associate the "Pasta Epson Printer Type" with the target printer(s).
a) Responsibility = System Administrator
b) Navigate --> Install: Register
c) Query the traget printer's name
d) Update the printer "Type" field with the "Pasta Epson Printer Type"
7. Bounce the concurrent manager.
Reference:
Note 739186.1 |
| posted by Jaswinder Singh @ 5:48 PM |
|
|
|
| Pasta Configuration to setup the printer in Oracle Applications !!!!! |
| Thursday, July 2, 2009 |
-> Printer should be setup at the operating system level .Use lpstat –a command
and check if the printer is configured as OS level.
To check if printer is printing at OS level use the following command:
Lp -d
-> File name can be any text file (ex any .req file $APPLCSF/$APPLLOG directory)
-> Network team and firewall team may need to be involved if the printer is not accessible from OS level.Only after printer is accessible from OS level we can configure Pasta to use the printer.
Configuration:
-> The version of pasta can be checked from $FND_TOP/bin
FNDPSTAX is the executable program for pasta.
FNDPSTAX -v
Pasta version 3.0.4.0 - unicode/bidi printing utility.
Copyright (c) Oracle Corporation 1999-2003.
-> Pasta patch is provided as standard AD patch of Oracle Applications and it needs to be applied on the concurrent processing node.
-> Patch 3325651 provides the above pasta release.
-> Setting up your system to use Pasta is much simpler than the standard Oracle Applications printer setup procedure. The Printer Type, Printer Driver, and SRW driver files are provided. The only setup required to begin printing is the registration of the printer with Oracle E–Business Suite.
-> Pasta comes with default Printer type:
Responsibility: System Administrator Menu Path: Install->Printer->Type
--PASTA Universal Printer Type. We can use the same printer type or configure a new printer type.
-> Associate the printer type with different printers as required.
Responsibility: System Administrator Menu Path: Install->Printer->Register
Example :
* Login in As sysadmin
* Navigate => System Administrator => Install : Printer => Register
Printer :
Type : --PASTA Universal Printer Type
Description :
-> Pasta configuration files are located in $FND_TOP/resource directory.
Pasta looks for files pasta_.cfg file in the above directory.
If the file is not present it will look for the file pasta.cfg
-> You can change the file that is defined as the default configuration file for Pasta by using the –F command line parameter.
For example, suppose you create a PCL print–specific configuration file
named pcl.cfg. Set the FNDPSTAX command line option as follows: –Fpcl.cfg
Pasta will look for pcl_.cfg first, and if it is not found,
Pasta will use pcl.cfg as the default.
These files must be placed under the $FND_TOP/resource directory.
The –F command line parameter can be set in the Arguments field of
the Printer Drivers window.
Pasta_pdf.cfg is the file used by pasta to print pdf converted to postscript
By 3rd party utility.The driver name is PASTA_PDF.
Ex:
In pasta_pd.cfg : preprocess=pdf2ps {infile} {outfile}.
-> The configuration file Pasta.cfg file governs many printing options.The file is a simple ASCII text file.
Some important options :
1. OutputFormat = ps/text ( ps stands for printers which support postscript format and text stands for printers which doesnt support post script Format)
2. Preprocess = ( Ex: pdf2ps utility To convert pdf to postscript )
3. Printcommand = lp (Print command for unix platform)
4. Pagewidth
5. pageheight .
There are lot of other options which can be configured like fontname, font size.
Note :
* During first time setup of pasta make sure all the information regarding the Printer is available and OS level pringting is working (Using lp command) before configuring pasta.
* For most of the changes made to configuration files it is necessary to bounce concurrent manager for changes to take effect. |
| posted by Jaswinder Singh @ 10:37 AM |
|
|
|
| Automatically deleting _pages !!!!! |
| Wednesday, June 24, 2009 |
1. Take the backup of adapcctl.sh file located in $COMMON_TOP/admin/SID_HOSTNAME
2. Make following changes in adapcctl.sh for automatically deleting _pages whenever we shutdown the apache.
3. Implement this before exit_code
if [[ "$control_code" = "stop" ]] ; then
DIR=`grep _pages $APACHE_TOP/Jserv/etc/zone.properties|grep -v "^#"|awk -F"="'{print $5}'`
if [[ -d $DIR ]]; then
echo $DIR
mv $DIR ${DIR}_`date +%F_%H_%M`
fi
fi
4. If you have worked in 11i, you might have done many times, clearing the caches by running rm -rf $COMMON_TOP/_pages/*
5. But in R12 if you do that, your login page will not come up, You will see blank screen.Why? In R12, on the fly compilation of JSP's are disabled.
6. In R12, by default, s_jsp_main_mode is set justrun Instead of recompile (which is 11i setting) in $CONEXT_FILE which will be propagated to oacore config file
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml
7. When main_mode = justrun the OC4J container running the OACoreGroup is told that no compilation on the fly is allowed and only (pre)compiled classes are picked up.
Since this requires less checks to be done the performance is improved. Therefore is this the recommended setting for a Production environment where JSP's will only be replaced occasionally.
8. compilation of Jsp's can be done by,$FND_TOP/patch/115/bin/ojspCompile.pl --compile --quiet |
| posted by Jaswinder Singh @ 6:11 AM |
|
|
|
|
|
