Agile PLM - Web Proxy Server Installation

It has been a while since I've posted about Agile PLM stuff.. In this post I'll go through implementing and configuring an Oracle Agile PLM Web Proxy Server. Previous related posts: Agile PLM 9.2.2.1 - Part I - Introduction Agile PLM 9.2.2.1 – Part II – Database Node Installation Agile PLM 9.2.2.1 – Part III – Application Node Installation First, who needs a Web Proxy server for Agile PLM? In order to make Agile PLM accessible to external users, a Web Proxy server should be installed to allow connections from the internet. This solution include a new server on DMZ behind a firewall which forwards calls to the internal Agile application server. (* Image from Oracle Agile documentation) The Agile Web Proxy Server installation consists of the following steps: Installing and Configuring the IIS Install the Agile Web proxy files on the IIS server in the DMZ Configuring IIS as a Proxy Server for Agile PLM Configuring IIS as a Proxy Server for Agile File Manager Create new external File Manager   Now I'll show a detailed procedure to install Agile Web Proxy Server on Windows using IIS (Microsoft Internet Information Server). *** When installing on Unix/Linux OS you'll use Apache as the web proxy server. Installing and Configuring the IIS Install IIS on the new Agile Proxy Server (will be called agiledmz) Login to agiledmz server with administrator user Navigate to: Start -> Administrative Tools -> Internet information services (IIS) Manager Right click on Web Sites -> new -> Web Site -> Next     Enter description: Agile PLM Web Site -> Next   Enter the following: Ip: All unussigned port: 80 host: null -> Next Path: C:\Inetpub\wwwroot -> Next   Check the Read option only -> Next   Click Finish   Right click on Agile PLM Web Site -> properties Select tab Directory Security -> Under 'Authentication and Access Control' click on Edit -> Uncheck the 'Integrated Windows authentication'   Disable the default Web Site:  Right Click on Defaule Web Site -> Stop   Install the Agile Web proxy files on the IIS server in the DMZ Make sure IIS is up and running (Go to services screen - services.msc - and check that "IIS Admin Service" process is in Started state)   Execute setup.exe from [INSTALLATION_BASE_DIR]\PN00168\Windows directory   Click Next -> accept the license -> Next   Enter User name, Company name and License key -> Next   Check the Web Proxies only -> Next   Specify directory on which agile files will be installed (D:\Agile\Agile9221)-> Next   Select Oracle Application Server 10g -> Next   Enter the Web Proxy server name (or IP) and port (80) -> Next   Enter the server name and port on which Agile application is installed (The Agile Application Server) -> Next   Keep the default "Agile" for Agile Application Server Virtual Path-> Next   Keep the default "Use internal user account (ifsuser)" -> Next   Keep the default "Filemgr" for Agile Primary File Manager’s Virtual Path -> Next   Enter Agile's File Manager host name and port (might be the same as Agile Application Server)-> Next   Click on Install Click on Done   Configuring IIS as a Proxy Server for Agile PLM Navigate to: Start > Administrative Tools > Internet Information Services (IIS) Manager Right click on Agile PLM Web Site -> properties Click the Home Directory tab -> update the execute permissions to Scripts and Executables   Click the ISAPI Filter tab -> click Add  Filter name: oproxy , Executable: D:\Agile\Agile9221\AgileProxies\oracle_proxy.dll -> Ok -> Ok   Right click on Agile PLM Web Site -> New -> Virtual Directory -> Next   Alias: oproxy -> Next   Path: D:\Agile\Agile9221\AgileProxies -> Next   Check the Read and Execute -> Next -> Finish   Select the Web Service Extensions -> Select the All Unknown ISAPI Extensions -> Click Allow -> Click Yes   Close IIS Manager window Restart IIS from services screen Right Click on Agile PLM Web Site -> properties -> select the ISAPI Filters tab -> you should see a green arrow pointing up for oproxy.     Configuring IIS as a Proxy Server for Agile File Manager Login to the File Manager server Note the Connector Port number from [AGILE_HOME]\Tomcat\conf\server.xml   <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->     <Connector port="8009" enableLookups="false" redirectPort="8443" debug="0" protocol="AJP/1.3"/> Edit jk2.properties from [AGILE_HOME]\Tomcat\conf Add the following line at the end and save the file: channelSocket.port=8009     Login to agiledmz - (The Web Proxy Server) Navigate to: Start > Administrative Tools > Internet Information Services (IIS) Manager Right click on Agile PLM Web Site -> properties Click the ISAPI Filter tab -> click Add Filter name: Jakarta IIS Connector , Executable: D:\Agile\Agile9221\AgileProxies\isapi_redirect.dll -> Ok -> Ok   Right click on Agile PLM Web Site -> New -> Virtual Directory -> Next   Alias: Jakarta -> Next Path: D:\Agile\Agile9221\AgileProxies -> Next Check the Read and Execute -> Next -> Finish   Open the workers.properties file in [AGILE_HOME]\AgileProxies and make sure the File Manager server is correct in the following entry:   worker.ajp13w.host=<File Manager host name>     Restart IIS  Right Click on Agile PLM Web Site -> properties -> select the ISAPI Filters tab -> you should see green arrows pointing up for both oproxy and jakarta.     Create new external File Manager Open the Agile Java Client Select 'Admin' Tab -> expand 'Server Settings' -> open 'Locations' Select the 'File Manager' tab -> click on the 'new' icon (you must have license for unlimited File Managers to enable it) Enter the following: Name - iFS_External File Manager URL - Use the web proxy server name (registered on the web) or IP, e.g. http://agile.company.domain/Filemgr/AttachmentServlet or http://111.11.11.111/Filemgr/AttachmentServlet Enabled - Yes Primary File Server - No   Click on 'Ok' Expand the 'User Settings' -> open 'Users' -> find the user you want to use the external iFS and open his settings -> select the 'Preferences' tab -> update the 'Preferred File Manager' to 'iFS_External'.   *** Important Note Agile architecture compels you to configure specific File Manager for each user. Users configured to use the internal iFS will be able to utilize the File Manager from within the network only! They'll be unable to utilize the external iFS when login to Agile through the Agile Web Proxy Server. The same behaviour for users configured to use the external iFS - They will be able to utilize the external iFS only.   Now you can login to agile from the internet through the Agile Web Proxy Server. Use the following URL to get the login screen:   http://[Agile Web Server Proxy IP or Name]/Agile/PLMServlet Next post I'll show how to secure connections to Agile through the Proxy server using SSL (https) connection. You are welcome to leave a comment and/or share your experience with Agile installation. Aviad

Developer 6i Patch Set 19 upgrade with EBS 11i

It has been more than two years since the last Developer 6i patchset 18 was certified with Oracle E-Business Suite Release 11i, and now, Developer 6i patchset 19 (6.0.8.28) is certified with Oracle Apps 11i. Actually, since we migrated from Jinitiator to Java JRE 1.6, we've encountered some frustrating mouse focus issues, I really hope they were fixed with this patch and won't appear after upgrade. Like with the last patch set, I'll bring you "step-by-step" upgrade instructions for linux deployments. Other Operation Systems's need another patches - see Note 125767.1 - Upgrading Developer 6i with Oracle Applications 11i. *** All patches must be installed on all Application tier nodes Stop all application processes by adstpall.sh   Apply the latest certified Developer 6i patch set 19 (6194129)  - Source applications environment (e.g source .../testappl/APPSORA.env)  - Verify that $ORACLE_HOME is the 806_ORACLE_HOME - Execute with applmgr user $ unzip p6194129_60828_LINUX.zip $ cd developer6i_patch19 $ ./patch_install.sh 2>&1 | tee patch_install_p19.log         - Check patch_install_p19.log for any errors - Execute the following to relink Procedure Builder, Forms, Graphics and Reports $ cd $ORACLE_HOME/procbuilder60/lib; make -f ins_procbuilder.mk install $ cd $ORACLE_HOME/forms60/lib;       make -f ins_forms60w.mk install $ cd $ORACLE_HOME/graphics60/lib;    make -f ins_graphics60w.mk install $ cd $ORACLE_HOME/reports60/lib;     make -f ins_reports60w.mk install           Apply patch 7156414  - Unzip patch file $ unzip p7156414_60828_GENERIC.zip         - Backup old files $ cp -r $ORACLE_HOME/forms60/java/oracle/forms/handler/UICommon.class $ORACLE_HOME/forms60/java/oracle/forms/ handler/UICommon.class.PRE_BUG7156414 $ cp -r $ORACLE_HOME/forms60/java/oracle/forms/handler/ComponentItem.class $ORACLE_HOME/forms60/java/oracle/forms/ handler/ComponentItem.class.PRE_BUG7156414 $ cp -r $ORACLE_HOME/forms60/java/oracle/forms/handler/BlockScroller.class $ORACLE_HOME/forms60/java/oracle/forms/ handler/BlockScroller.class.PRE_BUG7156414 $ cp -r $ORACLE_HOME/forms60/java/oracle/forms/handler/FormCanvas.class $ORACLE_HOME/forms60/java/oracle/forms/ handler/FormCanvas.class.PRE_BUG7156414 $ cp -r $ORACLE_HOME/forms60/java/oracle/forms/handler/FormWindow.class $ORACLE_HOME/forms60/java/oracle/forms/ handler/FormWindow.class.PRE_BUG7156414 $ cp -r $ORACLE_HOME/forms60/java/oracle/forms/ui/VBean.class $ORACLE_HOME/forms60/java/oracle/forms/ ui/VBean.class.PRE_BUG7156414          - Copy patch files to appropriate directories $ cd [PATCH_TOP]/7156414/oracle/forms/handler $ cp UICommon.class      $ORACLE_HOME/forms60/java/oracle/forms/handler/UICommon.class $ cp ComponentItem.class $ORACLE_HOME/forms60/java/oracle/forms/handler/ComponentItem.class $ cp BlockScroller.class $ORACLE_HOME/forms60/java/oracle/forms/handler/BlockScroller.class $ cp FormCanvas.class    $ORACLE_HOME/forms60/java/oracle/forms/handler/FormCanvas.class $ cp FormWindow.class    $ORACLE_HOME/forms60/java/oracle/forms/handler/FormWindow.class $ cd [PATCH_TOP]/7156414/oracle/forms/ui $ cp VBean.class         $ORACLE_HOME/forms60/java/oracle/forms/ui/VBean.class - Regenerate Jar files   - Execute adadmin   - Select the "Generate Applications Files menu" option   - Select "Generate product JAR files"   - Do you wish to force regeneration of all jar files? => Yes   - Spot check that the JAR files have been generated by verifying the timestamp     $ cd $OA_JAVA/oracle/apps/fnd/jar $ ll fndforms.jar fndewt.jar           Apply patch 6125732 - Unzip patch file + Apply patch $ unzip p6125732_60828_LINUX.zip $ cd 6125732 $ sh patch.sh         Apply patch 6857221 - Unzip patch file + Apply patch $ unzip p6857221_60828_LINUX.zip $ cd 6857221 $ sh patch.sh         - Relink f60webmx for Oracle Applications $ adrelink.sh force=y "fnd f60webmx"         Apply patch 3830807 - Unzip patch file + Apply patch $ unzip p3830807_8063_LINUX.zip $ cd 3830807 $ ./patch.sh         - Relink all Applications executables:   adadmin -> "Maintain Applications Files" -> "Relink Applications programs"   Apply patch 4586086 - Unzip patch file $ unzip p4586086_600_LINUX.zip         - Backup old file $ cd $ORACLE_HOME/forms60/lib $ mv env_forms60.mk env_forms60.mk.PRE_BUG4586086         - Copy patch file to the appropriate directory $ cd [PATCH_HOME]/bug4586086 $ cp env_forms60.mk $ORACLE_HOME/forms60/lib - Generate shared object + Relink f60webmx for apps $ cd $ORACLE_HOME/forms60/lib $ make -f cus_forms60w.mk libso_install $ adrelink.sh force=y "fnd f60webmx"          Relink applications executables - Run adadmin - Select (2) "Maintain Applications Files Menu" - Select (1) "Relink Applications programs" - List of product to link: fnd - Generate specific executables …: Yes - Relink with debug: No - Enter executables to relink: f60webmx ar60run ar60runb ar60rund   Apply patch 7343387 (Apps Interoperability) - Unzip patch file $ unzip p7343387_11i_GENERIC.zip         - Enable maintenance mode: adadmin -> (5) Change Maintenance Mode -> (1) Enable Maintenance Mode - apply patch with adpatch - Disable maintenance mode: adadmin -> (5) Change Maintenance Mode -> (2) Disable Maintenance Mode   Verify your upgrade - Check the timestamp for the following files: $ cd $OA_JAVA/oracle/apps/fnd/jar $ ll fndforms.jar fndewt.jar          If the timestamp is not current - run adadmin => Maintain Applications Files => Generate Product JAR Files.    Start all applications processes (adstrtall.sh) - You can also verify your upgrade by login to forms responsibility -> Help -> About Oracle Applications   You should see: Oracle Forms version : 6.0.8.28.0   Related - Note 125767.1 - Upgrading Developer 6i with Oracle Applications 11i. You are welcome to leave a comment

How to Configure OEM 10g Database Control after Clone

After cloning an EBS environment I had tried to start the OEM 10g Database Control (DBConsole) and I got this message: [oratest@testsrv1 ~]$ emctl start dbconsole TZ set to Israel OC4J Configuration issue. /oracle/test/db/testdb/10.2/ oc4j/j2ee/OC4J_DBConsole_testsrv1.domain_TEST not found. However, it was an acceptable message since DB Console wasn't configured to this instance yet. Using emca I've tried to recreate the DB Control configuration files as follow: [oratest@testsrv1 ~]$ emca -config dbcontrol db ... INFO: Database Control started successfully ... INFO: >>>>>>>>>>> The Database Control URL is http://testsrv1.domain:5500/em <<<<<<<<<<< Enterprise Manager configuration completed successfully Well, I thought it looks fine, but when I opened the DB Console I saw this message at the top of the page:  error: java.lang.Exception: Exception in sending Request :: null After some research, logs digging and Metalink searches, I found that the Agent component should be relinked manually. But before there are two issues in env_sysman.mk file that should be fixed before executing the relink command. I will show my actions step by step: Stop DB Console: emctl stop dbconsole   cd $ORACLE_HOME/sysman/lib   Edit env_sysman.mk and look for "JRE_LIB_DIR" In my instance JRE_LIB_DIR was populated with the old environment name.. I changed it from: JRE_LIB_DIR=/oracle/prod/db/proddb/10.2/jdk/jre/lib/i386 To: JRE_LIB_DIR=/oracle/test/db/testdb/10.2/jdk/jre/lib/i386   One more issue for env_sysman.mk, look for "$(LIBNMEM)  $(LIBNMER)" And change from: $(LIBNMEM)  $(LIBNMER) \ To: $(LIBNMEM)  $(LIBNMER) $(LIBNMO) \   Now relink the Agent component by issuing this command: make -f ins_sysman.mk agent   Recreate the DB Control configuration files (Again, even if you did it before) emca -config dbcontrol db Following this procedure will make the DBConsole configured and work for the new cloned instance.