ahmad.parvez@gmail.com Archive

CREATING ORACLE WALLET AND CERTIFICATE SIGNING REQUEST IN ORACLE OHS 12C USING COMMAND LINE INTERFACE orapki

CREATE A DIRECTORY WHERE YOU WILL SAVE YOU WALLET.

I have created  “wallet”   DIRECTORY UNDER ORACLE_HOME BY USING FOLLOWING COMMAND  <mkdir /u01/oracle/wallet>

RUN  SetDomainEnv.sh  SCRIPT THAT YOU WILL FIND  UNDER DOMAIN_HOME/bin  FOLDER

./setDomainEnv.sh

TO  CREATE A WALLET UNDER /u01/oracle/wallet  RUN THE FOLLOWING COMMAND  <u01/oracle/oracle_common/bin/orapki wallet create -wallet /u01/oracle/wallet -pwd Spring2016>

REMOVE DEFAULT CERTIFICATE FROM THE WALLET USING FOLLOWING COMMAND

/u01/oracle/oracle_common/orapki wallet remove -trusted_cert_all -wallet /u01/oracle/wallet

DISPLAY THE WALLET USING FOLLOWING COMMAND AND WALLET SHOULD BE EMPTY

</u01/oracle/oracle_common/orapki/ wallet display -wallet /u01/oracle/wallet

CREATE CSR  USING orapki COMMAND

</u01/oracle/oracle_common/orapki wallet add -wallet /u01/oracle/wallet/ -dn “CN=host01.lucknow.com,OU=Distributed,O=Business ,L=Atlanta,S=GA,C=US” -keysize 2048 -validity 1024

EXPORT CSR TO BE SIGN FROM SIGNING AUTHORITY

<./orapki wallet export -wallet /u01/oracle/wallet -dn “CN=host01.lucknow.com,OU=Distributed,O=Business,L=Atlanta,S=GA,C=US” -request ./host01.lucknow.com.csr

ONCE YOU RECEIVE THE SIGNED CERTIFICATE FROM YOU TRUSTED AUTHORIGHTY THEN ADD THAT CERTIFICATE IN THE WALLET

</u01/oracle/oracle_common/orapki wallet add -wallet /u01/oracle/wallet -user_cert -cert /u01/oracle/wallet/host01.lucknow.com.txt

Starting the WEBLOGIC Administration Server Using Node Manager and WLST IN 11G

  1. GO TO WEBLOGIC HOME  AND SET THE PATH ENVIRONMENT VARIABLE      1
  2. START WLST USING  java weblogic.WLST2
  3. NOW START THE NODEMANAGER USING COMMAND  startNodeManager.sh    YOU WILL SEE A MESAGE STATING   “INFO: Secure socket listener started on port 5556, host localhost/127.0.0.1”    <— WHICH MEAN NODEMANAGER HAS STARTED ON LOCAL HOST

4. Connect WLST TO NODE MANAGER USING FOLLOWING COMMAND.  ONCE CONNECTED YOU WILL SEE A MESSAGE STATING      “SECURE SOCKET LISTENER STARTED ON PORT 5556,  host localhost/127.0.0.1

4

5.   BY USING nmConnect   COMMNAD CONNECT NODEMANAGER TO WLST  — ONCE CONNECTED USING BELOW COMMAND   YOU    SHOULD GET A MESSAGE SAYING ‘Successfully Connected To Node Manager’

5

6.  RUN THE FOLLOWING COMMAND TO START ADMIN SERVER   nmStart(‘MedRecAdmSvr’)   AS SHOWN IN BELOW SCREEN SHOT

6

7. TO CHECK THE STATUS OF ADMIN SERVER  AND TO SHUTDOWN THE ADMIN SERVER THIS IS WHAT YOU WILL DO.

7

 

 

 

Cheer!!

Parvez Ahmad

 

INSTALLING PATCHES ON ORACLE HTTP SERVER(OHS) 11.1.1.9.0 USING OPATCH UTILITY PATCH#21663064

  1. FIRST OF ALL YOU NEED TO KNOW WHAT VERSION OF OHS CURRENTLY INSTALLED IN YOUR ENVIROMENT AND TO DO THAT RUN THE FOLLOWING COMMAND.

GO TO ORACLE_HOME/OPATCH  AND  RUN THE FOLLOWING COMMAND

cd  /u01/Oracle_Web/OPATCH/   RUN  <./opatch lsinventory>  AS SHOWN IN THE SCREEN SHOT.   I HAVE CIRCLED THE OHS VERSION IN GREEN

1

 

2. NEXT YOU NEED TO FIND OUT WHAT PATCHES ARE AVAILABLE  FOR 11.1.1.9.0 FROM ORACLE SUPPORT WEBSITE.

2

3.  FOR THIS VERSION HERE IS WHAT IS AVAILABLE.  I AM RUNNING OHS ON  RED HAT LINUX 64 BIT THEREFORE I HAVE SELECTED 64 BIT PATCH

2

4.  CLICK ON PATCH 21663064 FOR  64 BIT LINUX  AND START DOWNLOADING

4

5. I HAVE KEPT DOWNLOADED PATCH IN /u01/patches  AND UNZIP IT USING  unzip command.  After unzip command completed another folder with the name of 21663064 being created.

5

6. NOW LET’S INSTALL THIS PATCH AND TO DO THIS…  cd 21663064   and run command <opatch apply>  Make sure when you run this command ORACLE_HOME/OPATCH IS IN YOUR PATH

6

Enter yes when you get prompted for ” Is the local system ready for patching [y|n]  …  Once done you will get a message “OPatch succeeded.”  AS  SHOWN BELOW

8

9.  TO DOUBLE CHECK IF PATCH INSTALLED WAS SUCESSFUL YOU CAN LOOK INOT THE LOGS OR YOU CAN ALSO RUN <opatch lspatches>  COMMAND AS SHOW BELOW.  YOU WILL SEE THE INSTALLED PATCH IN THE LIST WHICH I HAVE CIRCLED IT WITH GREEN.

 

10

10.  NOW ROLLING BACK PATCHES QUITE SIMPLE.   RUN THE FOLLOWING COMMAND WITH INSTALLED PATCH NUMBER  </u01/Oracle_Web/OPatch/opatch rollback -id 21663064>

11

11) NOW YOUR PATCH SHOULD BE SUCCESSFULLY ROLLED BACK AND YOU CAN CHECK IT WITH RUNNING  SAME COMMAND <opatch lspatches>

12

NOTICE PATCH 21663064 IS NOT IN THE LIST ANYMORE AND HAS BEEN REMOVED.

How to create a Gridlink Datasource on Weblogic 12c

 

  •  12c RAC DATABASE
  • 12c WEBLOGIC SERVER
  • SCAN LISTENER  SHOLD BE CONFIGURE AND RESLOVING IP
  • FAN HOST NAME AND PORT
  1. GO TO DATA SOURCE AND CLICK ON NEW

1

2. CLICK NEW AND THEN PICK GRIDLINK DATA SOURCE FROM DROP DOWN LIST

2

3. GIVE NAME, JNDI NAME AND PICK *ORACLE’S Driver(ThinXA) for GridLink Connection Versions:Any

3

 

4. CLICK NEXT ON TRNSACTION OPTION SCREEN

4

5.  I  WILL CHOOSE Enter Complete JDBC URL  SINCE I  WILL BE USING SCAN IP

5

6. PROVIDE  COMPLETE JDBC URC: (jdbc:oracle:thin:@rac.scan.india.com:1521/service_id), PROVIDE DATBASE USER NAME & PASSWORD. Make sure user have connect resource in database

and CLICK NEXT

6

7. ON THIS SCREEN  LETS TEST THE CONNECTION  AND IF YOU CONFIGURATION IS RIGHT THEN AND THERE IS NOT ISSUE ON DATABASE SIDE THEN YOU SHOULD GET “Connection test for jdbc:orcle:thin:@@@@@@@@:1521/service_name  succeeded   ON THE TOP OF THE PAGE.  ONCE DONE TESTING CLICK NEXT

7

8. As next step, you have to enter the ONS client configuration. This step allows the data source to subscribe to and process Oracle FAN events; this is essential to distribute connection requests across RAC instances.   ONCE ENTER CLICK NEXT HERE

8

9. NOW LET’S TEST FAN CONFIGUATION  BY CLICKING EACH  Test ONS Node  CIRCLE IN GREEN AND IF IT YOU GET ” Connection test hostname:6200  succeed for each instance then you have configure it correctly. 9

10. CLICK NEXT ONE DONE TESTING BOTH CONNECTION AND DEPLOY  THE CONNECTION ON THE SERVER OR CLUSTER YOU WOULD LIKE IT TO

 

WEBSPHERE 8.5 NETWORK DEPLOYMENT CREATING PROFILES

CREATING PROFILES USING PROFILE MANAGEMENT TOOL

1.

screen1

2. Select Option Typical Profile Creation

screen2

4. Click Next on Profile Creation Summary

screen4

5. Installation Started

screen5

6. Profile  Creation complete click Finish

screen6

 

6. You Will Come To This Screen Which Confirming That AppSrv01 And Dmgr01 Two Profiles Has Been Created.screen7

7. Let’s start the Dmgr – Go to /opt/IBM/Websphere/AppServer/profiles/Dmgr01/bin and run ./startManager.sh script.    When you get a message stating “Server dmgr open for e-business porcees id is 8897 ”  that’s mean dmgr  up

screen8

8. You Can Access Cell Using  http://hostname:9060/ibm/console    you should get below screen.  To login click login since we didn’t define any user during our installation

screen9

9. Once You Login You Will See Following Screen.

screen10

10. Click On Websphere Application Server From Left Hand Panel, Notice  One App Server With The Name of server1  is Created During Our Installation.

screen11

 

 

 

 

 

Websphere 8.5 Network Deployment Installation Part2

  1. Run ./Install.sh  as show in below screen shotCapture
  2. Click Install

screen1

3. Select IBM WebSphere Application Server Network Deployment

screen24. Accept terms and condition here

screen3

5.  take default and click Next

screen4

6. take default and click Next

screen5

7. click Nextscreen5

8.

screen6

9. Click Install

screen8

10.   Installation started

screen9

12.  Installation completedscreen10