HOW TO ENABLE SSL IN QPID

HOW TO ENABLE SSL IN QPID

1.        Go to QPID Web Management Console by using url http://<qpid-ip>:<http-port>/ using guest/guest credentials. 

2.       Scroll down till “Key Stores” 

3.       Click on “Add Key Store” 

a.       Type: NonJavaKeyStore

b.      Private Key: <Upload Private Key>

c.       Certificate: : <Upload Certificate>

d.      Intermediate Certificate: <Leave it>

4.       Click on “Save”.

5.       Go to “Ports”

6.      Click on “Add Port”.

a.       Name*: <User choice>

b.      Port Type*: AMQP

c.       Port Number: <default NON-SSL port is 5672. User can use any open port for SSL>

d.      Protocols: <Select all>

e.       Authentication Provider*: <select Plain from drop-down>

f.        Binding address: <leave it>

g.      Transport: SSL

h.      Maximum number of connections: <leave it>

i.         Number of connection threads: <leave it>

j.         Key Store*: <Select kestore from drop-down we just created in step 3>

k.       Need SSL Client Certificate: <leave it>

l.         Want SSL Client Certificate: <leave it>

m.    Client Certificate Recorder: <leave it>

7.       Click on “Save Port”. Use tab to reach till Save Port

8.      Make sure that the State should be showing ACTIVE.

Find out API calls on Android device/emulator

Steps to validate API call on every emulator clicks:

1. Launch emulator, either through AVD manager or command line using D:\Projects\Utils\Android\sdk\tools>emulator.exe avd <avd-name>

2. Make emulator as proxy:

• Click on Menu
• Click on Settings
• Click on Wireless & Networks
• Go to Mobile Networks
• Go to Access Point Names
• Here you click on .
• In the Edit access point section, input the "Proxy (10.1.1.111) and Port(9090)

      
   
3.         Install and run Burp Suite. Go to Proxy->Options








4. Launch mobile application in emulator.
5. Go to Proxy->Intercept and click on “Intercept is off”.
6. Click on any link for which we want to get the API is getting called.
7. Burp will show them in Raw section.

 

Load test on sql server using JMeter.

Steps to put load on Sql Server 2005/2008 using JMeter.

Pre-requisites:

• Download Jmeter 2.8 and above
• Download JMeterPlugins.jar and copy it to apache-jmeter-<version number>\lib\ext.
• Precheck ojdbc-11.2.0.3.jar file in lib folder.

NOTE: Operating system used to run JMeter was Windows XP

Steps:

• Go to bin folder. (inside JMeter installed/unzipped folder)
• Open jmeter.bat file.
• Right click on Test Plan ans navigate till Add -> Threads(Users) -> Thread Group. Click on Thread Group.

• Again do right click on Test Plan ans navigate till Add -> Threads(Users) -> jp@gc - Ultimate Thread Group. Click on jp@gc - Ultimate Thread Group.

 

•  Click on jp@gc - Ultimate Thread Group and change Start Thread Count and Hold Load For, Sec to 60
• Right click on jp@gc - Ultimate Thread Group and select JDBC Request as show below.

 

• Go to JDBC Request page.
• Select Variable Name as BI.
• Select Query Type as Select Statement from drop down list.
• Mention your query in Query section you want to execute to put load on sql server.

• Right click on jp@gc - Ultimate Thread Group and select JDBC Connection Configuration as show below. 

 

• Go to DBC Connection Configuration page.
• Select Variable Name as BI. 
• Change Max Number Of Connections as per your requirement.
• Keep default configuration at all places except Database COnnection Configuration.
• In Database COnnection Configuration, do the changes as below:

• Database URL: jdbc:sqlserver://<IP of machine where sql server instance is running>:<sql server port number>;instanceName=<hostname/computer name>;databaseName=<database name where you want to execute the query>
• JDBC Driver class: com.microsoft.sqlserver.jdbc.SQLServerDriver
• Username: sa
• Password: <sa password>

• Add Listeners like Summary Report and View result Tree as show below.

 

 

Here we are done with jmx file configuration. Now start the JMeter and it will start pushing load on sql server.

 

Hope this blog will help users who wish to do load testing on sql servers.