How To Configure JDeveloper 11g to Invoke Secure Web Services? (Doc ID 1277326.1)

How To Configure JDeveloper 11g to Invoke Secure Web Services? (Doc ID 1277326.1) APPLIES TO: Web Services - Version 11.1.1.0.0 and later Oracle Weblogic Server - Version 11.1.1.1.0 and later Oracle JDeveloper - Version 11.1.1.0.0 and later Information in this document applies to any platform. GOAL How to configure JDeveloper11g to add an existing certificate/keystore to invoke a secure Web Service? SOLUTION Import the certificates, then specify the certificates/keys path in the Run Directory of the project by applying the following steps: Copy your certificate ( eg. certificate.cer ) to JDeveloper's internal JRE directory, for example: C:\Jdeveloper11.1.1.3.0\Oracle\Middleware\jdk160_18\jre\lib\security Import the certificate using the following command: keytool -v -import -file certificate.cer -keystore cacerts Invoke the project properties dialog of your Web Service (Client) project: Select Run/Debug/Profile. Click the button Edit. In the field Run Directory, specify the certificates, keys directory with the following path: C:\Jdeveloper11.1.1.3.0\Oracle\Middleware\jdk160_18\jre\lib\security Restart JDeveloper, and then invoke the secure Web Service.

How To Call a SSL Secured Web Service from JDeveloper 430414.1

How To Call a SSL Secured Web Service from JDeveloper 10.1.3.x ? (Doc ID 430414.1) To BottomTo Bottom In this Document Goal Fix APPLIES TO: Web Services - Version 10.1.3.0.0 to 10.1.3.4.0 Oracle JDeveloper - Version 10.1.3 to 10.1.3.5.0 Information in this document applies to any platform. ***Checked for relevance on 26-Jan-2010*** ***Checked for relevance on 12-Oct-2012*** GOAL How to call a Web Service that is secured by SSL, and that uses certificates. You have the certificate stored in a keystore and have generated a Web Service Proxy using the wizard in JDeveloper. FIX 1. Start a new JDeveloper project and create the Web Service Proxy. 2. Right-click the project node in Application Navigator and select Project Properties ... 3. Select Run/Debug 4. Click New to create a new Run Configuration 5. Enter a name and click Ok 6. Select the new Run Configuration and Click Edit 7. On the Launch Settings page, enter the following in the java options text box -Djavax.net.ssl.trustStore="" -Djavax.net.ssl.trustStorePassword="" -Djavax.net.ssl.keyStore="" -Djavax.net.ssl.keyStorePassword="" Ensure that the Web Service provider's certificate is added in your truststore as a trusted certificate. 8. Click Ok 9. Click Ok to use the new configuration. 10. Run the application and test. NOTE: Even though it is not the purpose of this document, if an explanation is necessary on how to use the JDeveloper wizard to create a Web Service proxy, the Oracle SOA Suite Developer's Guide 10g provides a good explanation at the following URL: http://docs.oracle.com/cd/B31017_01/core.1013/b28764/web_services003.htm#CHDBABBJ For assistance with the creation and manipulation of keystores using keytool, the Java 6 SE documentation provides some guidance at the following URL: http://docs.oracle.com/javase/6/docs/technotes/tools/windows/keytool.html

Configuring Jdeveloper 11g to work with SSL

Configuring Jdeveloper 11g to work with SSL Configuring Jdeveloper 11g to work with SSL Many times we come across situations where we need to create connection to SSL enabled weblogic server and deploy the code. Here I would like to show steps I have followed to setup Jdev for SSL. Get the server certificate preferably in '.cer' extension.If you have certificate installed in your browser then you can simply export it(Tools->Internet Options->Content then certificates) Copy certificate into any local folder, assume that D:\certificates Open DOS prompt and import certificate into Jdev certificate trust store DOS:\>keytool -import -alias democert -file D:\Certificates\ -keystore D:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -storepass DemoTrustKeyStorePassPhrase Parameters explanation democert is some alias name I have given to my certificate DemoTrustKeyStorePassPhrase is default key store password D:\Oracle\Middleware\wlserver_10.3 is my Integrated WLS home that comes with Jdev DemoTrust.jks is default certificate store comes with WLS(Weblogic server) List certificate in store Open DOS and run below command D:\Oracle\Middleware\jdk160_29\bin>keytool -list -keystore D:\Oracle\Middleware\ wlserver_10.3\ server\lib\DemoTrust.jks Cross check output returned by above command has your certificate If it doesn't list your certificate then import was not successful and you need to make sure import happens successfully We need to import same certificate in below keystore also JDK_HOME\bin>keytool -import -alias -file < certificate file path > -trustcacerts -keystore JDK_HOME\jre\lib\security\cacerts Default pwd will be changeit Restart Jdev and try to create connection to Jdev Note: When you create WLS connection in Jdev please choose 'Always use SSL' and enter SSL Port If you still see issues with creating connection then please follow steps mentioned at Oracle support document-ID 1338707.1 Document says- We need to clean profile and preferences then re create connection again by the following steps: Close Jdeveloper Navigate to following path-C:\Documents and Settings\\Application Data\JDeveloper\system11.1.1. x.x.x.x.x Note : Here x.x.x.x.x is some numbers If you dont find above path then try to search for folder with name starting with 'system11.1.1' Rename this directory to any other name Restart Jdeveloper Try to create connection Now we will have a jdev thats totally clean with preferences set to default values http://soacrux.blogspot.com/2012/09/configuring-jdeveloper-11g-to-work-with.html

2014: A Year in Review for Oracle E-Business Suite

https://blogs.oracle.com/stevenChan/entry/op_faq2 2014: A Year in Review for Oracle E-Business Suite By Steven Chan (Oracle Development) on Dec 31, 2014 Happy New Year. 2014 was another big year for the Oracle E-Business Suite. Did you miss any of the most-important articles of the year? Upgrading to EBS 12.2 • Three Essential Reference Tools for E-Business Suite Upgrades • Preparing Your Customizations for EBS 12.2 • Top 9 Frequently-Asked Questions About Online Patching • Top Three EBS 12.2 Online Patching Resources • Three Options For Getting to Oracle E-Business Suite Release 12.2 • New 12.2 EBS Technology Stack Documentation Roadmap Available Updates to EBS 12.2 • Oracle E-Business Suite 12.2.4 Now Available • New User Interface Features in Release 12.2.4 • EBS 12.2.4 OA Extensions for Jdeveloper 10g Now Available • E-Business Suite 12.2.4 VM Virtual Appliances Now Available • New Rapid Install StartCD 12.2.0.49 for EBS 12.2 Now Available • November 2014 Updates to AD and TXK for EBS 12.2 • Updated Whitepaper: Using Application Express with EBS 12.2 • Integrating Custom and Third-Party Products With EBS 12.2 Updates to EBS 12.1 • Second Recommended Patch Collection for EBS 12.1.3 Now Available • First Recommended Patch Collection for EBS 12.1.3 Now Available • New OA Framework 12.1 Release Update Pack 4 Now Available • New Patch Wizard for EBS 12.1 Now Available Java • Java Auto-Update Upgrades JRE 7 to 8 in January 2015 • Java (JDK) 7 Certified with E-Business Suite 12.2 Servers • Java JRE 8 Certified with Oracle E-Business Suite • JRE Support Ends Earlier than JDK Support Important Technology Stack Updates • Mobile Apps for Oracle E-Business Suite • Microsoft Office 2013 Certified with E-Business Suite 12.1.3 • Microsoft Office 2013 Certified with E-Business Suite 11i • Microsoft Office 2013 Certified with E-Business Suite 12.0.6 • Microsoft Office 2013 Certified with E-Business Suite 12.2 • Updated: Using Third-Party Identity Managers with E-Business Suite Release 12 • Oracle Functional Testing Suite Advanced Pack for EBS 12.2.4 Now Available • Oracle EBS Adapter for Oracle SOA Suite 12c Now Available • Application Management Pack 12.1.0.2 Certified with EM 12cR4 • E-Business Suite Plug-in 12.1.0.3 for Enterprise Manager 12c Now Available • New Solaris SPARC OS Requirements for EBS R12 • Google Chrome 35 Certified with Oracle E-Business Suite 12.1 & 12.2 • Internet Explorer 11 Certified with E-Business Suite 12.1 • Database 12.1.0.1 Certified with EBS 12.2 • Database 12.1.0.2 Certified with E-Business Suite 12.1 • Oracle Database 11.2.0.4 Certified with E-Business Suite 12.2 Virtualization • Oracle VM Virtual Appliances Available for E-Business Suite Release 12.2.3 • Oracle VM Templates For EBS 12.2.3 For Exalogic • Oracle VM Virtual Appliances for E-Business Suite 12.1.3 Now Available • EBS VMs: Appliances, Templates, and Assemblies Explained • E-Business Suite 12.2.4 VM Virtual Appliances Now Available Maintaining and Extending EBS • Understanding and Managing Licensing Options in Oracle E-Business Suite • Creating a Maintenance Strategy for Oracle E-Business Suite • Oracle Functional Testing Suite Advanced Pack for Oracle EBS Now Available • Testing Your EBS Environment After Database Upgrades • Which JDeveloper Version Works With Your EBS Release? • A Primer on Oracle E-Business Suite REST Services Support Policies • After Windows XP and Office 2003: E-Business Suite Implications • JRE Support Ends Earlier than JDK Support • Support Implications for Your EBS Customizations

Configure Oracle Internet Directory 11gR1 with Oracle E-Business Suite Release 12.2.

Configure Oracle Internet Directory 11gR1 with Oracle E-Business Suite Release 12.2. Step 1: Before starting with the configuration start an Online Patching Cycle using ADOP Step 2: Choose Registration Type - Default (Simple) or Advanced Step 3: Compile Parameter Checklist Step 4: Run the Environment Script for the Patch File System Step 5: Check Specific Environment Settings Step 6: Run the Registration script from Patch File System Step 7: Confirm Successful Script Completion Step 8: Set the following profiles options in Oracle E-business Suite Release12.2 from Patch File System Step 9: Run Autoconfig from the Patch file system Step 10: End ADOP Patching Cycle(cutover) Will post the steps in detail .

Oracle EBS 12.2 Online Patching

Refer :http://www.strsoftware.com/blog/oracle-ebs-12-2-online-patching-first-glance Anyone that’s been following the release of 12.2 knows that Online Patching is the BIG feature that everyone is talking about. I’ve had the opportunity to utilize this new functionality and it’s been quite interesting. Online Patching is based on the Oracle Database 11.2 feature called Edition-Based Redefinition. The patch process has completely changed. There is now a patch edition and a run edition in the database. Additionally, the filesystem itself has 2 editions, a patch and run edition (there’s also one other filesystem that is non-editioned). There are 5 major steps in the patching process. Prepare – Creates the patch edition. Apply – Applies the patches to the patch edition Finalize – Ensures the system is ready for cut over (from patch to run edition) Cutover – This is where the patch edition becomes the run edition. Cleanup – Removes unnecessary code from obsolete editions. Steps 1-3 can be run while users are actively using the system. All of the patching is done in the patch edition of both the database and file system. Users essentially have no clue that patching is happening. Step 4 does require users to be booted off the system as the physical cutover is performed making the patch edition the new run edition, but this time should be nominal as all of the time consuming patching has already occurred in Steps 1-3. Additionally, the cutover process can be scheduled anytime after steps 1-3. For example you could take care of Steps 1-3 and then wait a week for an optimal time to run the actual cutover itself. Step 5 also does not require the system to be down and can be run anytime after the cutover and before the next prepare phase. One of the features of EBR is the ability to have certain users using the new functionality while other users use the old, non patched functionality. I was pretty excited about this. What a great way to test patches in the wild right? Give access to some power users to the patch edition and let them have it to really test it out. Unfortunately, this particular feature of EBR does not seem to be available in the online patching functionality of EBS. Users are quarantined to the RUN edition only. This new patching methodology is going to be mean changes for a lot of people. Both 3rd parties like STR Software that have bolt on products and individual companies that are maintaining customizations will require modifications to their code base to support Online Patching. I am currently going through the process of determining what those changes are and what they mean to our product and installation/upgrade scripts. I will likely have more comments on that subject once I’m further along in my investigation! For now, if you’ve been maintaining and patching previous versions of EBS and you are moving to 12.2, I would highly recommend that you thoroughly read the Oracle EBS Concepts Guide and Oracle EBS Maintenance Guide focusing on the patching and filesystem sections as everything has changed. It will give you a good primer as to what you are in for! Please watch the below youtube video whihc will give you more information about 12.2 Patching .. https://www.youtube.com/watch?v=kXLkna6GbQY adop phase=prepare Note:‐ In case, the previous patch cycle did not complete its cleanup phas, The new adop prepare phase will execute the clean‐up phase of previous cycle, if needed, and then proceed with preparing the new patch edition for new Online patching cycle. Create a new database patch edition Synchronize the file system patch edition with the run edition Configure the patch edition for use by the patching tools File system synchronization may be done by applying the delta (changes) from the previous patching cycle, or by re‐creating the entire patch edition file system as a fresh copy of the run edition (called "fs_clone"). When complete, check the exiting status code (success is '0'): adop exiting with status = 0 (Success) Once prepare phase is complete, the database and file system patch edition will contain a copy of the run edition code and seed data. 2) Apply ‐ apply ARU or manual patches to the patch edition. Below steps can be followed for ARU Patches Download the patch bundle from ARU from metalink. SCP the ZIP files in the "fs_ne/EBSapps/patch" directory on the Middle‐tier Use "adop phase=apply" command for patch application. >adop phase=apply patches=12345678 ... adop phase=apply patches=12345678,12312345 ... Below steps can be followed for Manual Patches. Manual patching is similar to our old R12.1 or 11i methods but the only difference being that the update happens in the patch edition only. Copy patch files to their destination directories in the patch edition. Execute any commands necessary to deploy changes to the file system. Execute any commands necessary to deploy changes to the database Update the custom synchronization driver to include any file system actions that must be executed again on the next prepare phase, in order to synchronize the alternate file system. Note:‐ The above steps can be automated using code migration tools like HP PPM Kintana or Dell Stat or Any other tools. My Favourite is HP PPM tool  (Its deployment module). 3) Finalize ‐ perform any actions required to prepare for cutover.  The finalize phase is used by the Online Patching system to perform any final actions needed to make the system ready for the fastest possible cutover. The finalize command is run as follows: [ajithpathiyil1:ajithebs:applmgr]> adop phase=finalize The finalize command should not have any error, In case of error, the system is not ready for cutover  After successful completion of the finalize phase, the system is ready for cutover Note:‐ We do not need to execute the cutover immediately; Cutover can be delayed until a convenient time in the future. In the meantime, We may also apply additional patches if needed, but you will need to run the finalize phase again after doing so. 4) Cutover ‐ Promote Patch Edition to be the new Run Edition.  The cutover phase will configure the patch edition to become the new run edition, and restart the application on this new run edition. Note:‐ Since the run/patch designation of the dual file systems are swapped during cutover, you must re‐source the run edition environment directly after cutover. adop phase=cutover ... ]> . /u02/app/applmgr/120//EBSapps.env run EBusiness Suite Environment Information RUN File System : /u02/app/applmgr/120//fs1/EBSapps/appl PATCH File System : /u02/app/applmgr/120//fs2/EBSapps/appl NonEditioned File System : /u02/app/applmgr/120/ajithebs/fs_ne DB Host: abc.lab.com Service/SID: abcebs Sourcing the RUN File System ... 5) Cleanup ‐ remove obsolete code and data from old editions. The cleanup phase will remove unnecessary code and data from old editions that are no longer needed by the running application. Cleanup should be run after cutover, at any time before the next prepare phase. It is best to run cleanup immediately after cutover so that there is no delay when preparing the next online patching cycle. There are two levels of cleanup available: quick ‐ the minimal cleanup required before starting the next patching cycle. full ‐ removes all obsolete code and data to recover maximum free space. Quick cleanup is the default, and is all that is necessary after normal patching.

what is LDOM and CDOM

https://blogs.oracle.com/cmt/entry/what_s_up_with_ldoms What is Hypervisor??? Hypervisor is a thin firmware layer that provides a stable virtualized machine architecture to which an operating system can be written. It resides in the flash PROM of the motherboard and act as interface between operating system and the hardware. It provides a set of support fuctions to the operating system, so that the OS does not need to know intimate details of how to perform fuctions with the hardware. What is Logical Domain??? Logical domain is a discrete logical grouping with its own operating system, resources and identity within a single computer system. Each logical domain can be created, destroyed, reconfigured, and rebooted independently, without requiring a power cycle of the server. We can run a variety of applications software in different logical domains and keep them independent of performance and security purposes. What is Logical Domains Manager??? The Logical Domains Manager is used to create and manage logical domains. There can be only one Logical Domains Manager per serer. The Logical Domains Manager maps logical domains to physical resources. What is Control Domain??? Domain in which the Logical Domain Manager runs allowing you to create and manage other logical domains and allocate virtual resources to other domains. There can be only one control domain per server. The initial domain created when installing Logical Domains software is a control domain and is named primary. What is Service Domain??? Domain that provides virtual device services to other domains, such as a virtual switch, a virtual console concentrator, and a virtual disk server. What is I/O Domain??? Domain that has direct ownership of and direct access to physical I/O devices, such as a network card in a PCI express controller. Shares the devices with other domains in the form of virtual devices when the I/O domain is also the control domain. What is Guest Domain??? Domain that is managed by the control domain and uses services from the I/O and service domains. Patch Installation Refer the Logical Domains 1.0.2 Release notes for the required patches/softwares for your OS release http://mysolarisworld.blogspot.com/p/how-to-install-and-configure-ldom.html