How to get Windows version using cmd

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"

How to create CSR with SANs using keytool

Step1: Generating the Key

keytool -genkey -keystore Identity_trust.jks -storepass srinfosolutions -alias 192.168.0.3 -validity 365 -keyalg RSA -keysize 2048 -dname "CN=192.168.0.3,OU=IT,O=Dell USA L.P.,L=SRInfo,ST=Texas,C=US" ext SAN=dns:192.168.0.4,dns:192.168.0.5

step2 - create request file (.csr) file usinng keytool command 

keytool -certreq -alias 192.168.0.3 -storepass srinfosolutions -keyalg RSA -file certreq.csr -keystore Identity_trust.jks

Domain creation in weblogic 12c

Weblogic domain is an administrative unit on Weblogic Platform.Each domain must have one Administration Server.Administration server will administrate the domain, all the field configurations and deployments will store under Administration server.
Other than administration server all other servers we called as Managed Servers.


Here is the script to create Weblogic Domain

step1: save the below script as domain_creation.py

step2: java $oracle_come/common/bin/wlst.sh domain_creation.py

Note: if java not setup please setup java calss path 

export PATH=java_home path


#=======================================================================================
# Usage: 
#      java weblogic.WLST <WLST_script> 
#
# Where: 
#      <WLST_script> specifies the full path to the WLST script.
#=======================================================================================

#=======================================================================================
# Open a domain template.
#=======================================================================================

readTemplate("/u02/jenkins/oracle12c_r2/mw_home/oracle_home/wlserver/common/templates/wls/wls.jar")

#=======================================================================================
# Configure the Administration Server and SSL port.
#
# To enable access by both local and remote processes, you should not set the 
# listen address for the server instance (that is, it should be left blank or not set). 
# In this case, the server instance will determine the address of the machine and 
# listen on it. 
#=======================================================================================

cd('Servers/AdminServer')
set('ListenAddress','aussoaditapp16.us.dell.com')
set('ListenPort', 25019)

create('AdminServer','SSL')
cd('SSL/AdminServer')
set('Enabled', 'True')
set('ListenPort', 25020)

#=======================================================================================
# Define the user password for weblogic.
#=======================================================================================

cd('/')
cd('Security/base_domain/User/weblogic')
cmo.setPassword('jenkins@domain1')
# Please set password here before using this script, e.g. cmo.setPassword('value')

#=======================================================================================
# Create and configure a JDBC Data Source, and sets the JDBC user.
#=======================================================================================
#set('URL','jdbc:derby://localhost:1527/db;create=true')
#set('PasswordEncrypted', 'PBPUBLIC')
#set('UseXADataSourceInterface', 'false')
#create('myProps','Properties')
#cd('Properties/NO_NAME_0')
#create('user', 'Property')
#cd('Property/user')
#cmo.setValue('PBPUBLIC')

#cd('/JDBCSystemResource/myDataSource/JdbcResource/myDataSource')
#create('myJdbcDataSourceParams','JDBCDataSourceParams')
#cd('JDBCDataSourceParams/NO_NAME_0')
#set('JNDIName', java.lang.String("myDataSource_jndi"))

#cd('/JDBCSystemResource/myDataSource/JdbcResource/myDataSource')
#create('myJdbcConnectionPoolParams','JDBCConnectionPoolParams')
#cd('JDBCConnectionPoolParams/NO_NAME_0')
#set('TestTableName','SYSTABLES')

#=======================================================================================
# Target resources to the servers. 
#=======================================================================================

#cd('/')
#assign('JMSServer', 'myJMSServer', 'Target', 'AdminServer')
#assign('JMSSystemResource.SubDeployment', 'myJmsSystemResource.myQueueSubDeployment', 'Target', 'myJMSServer')
#assign('JDBCSystemResource', 'myDataSource', 'Target', 'AdminServer')

#=======================================================================================
# Write the domain and close the domain template.
#=======================================================================================

setOption('OverwriteDomain', 'true')
writeDomain('/u02/jenkins/domains/jenkins_domain')
closeTemplate()

#=======================================================================================
# Exit WLST.
#=======================================================================================

exit()

How to Disable/Enable ProxyService in OSB 12c

Before 12c in older versions if we want to enable/disable ProxyService we need to login sbconsole.

But in 12c that option moved to EM console.

Here are the steps to enable/disable ProxyService.

1) Login to EM console 

2) Navigate to OSB Project--> Operations tab

3) Select the ProxyService and enable or disable checkbox for state option.

What is DataPower?

IBM WebSphere DataPower SOA Appliances are purpose-built, easy-to-deploy network devices that simplify, help secure, and accelerate your XML and Web services deployments while extending your SOA infrastructure.

IBM WebSphere DataPower Family Suite

1.DataPower XML Accelerator XA35

2.DataPower XML Security Gateway XS40   

                             

3.DataPower Integration Appliance XI50  (Note : XI50 in itself has the capabilities of XS40 and XA35)

                            

4. DataPower GateWay XI52

                           

5.B2B Appliance XB60

6.Low Latency Appliance XM70

 Features of XA35,XS40 and XI50 & XI52 Appliances

1.DataPower XML Accelerator XA35

         1.Accelerates SOA and Web services deployments

         2.Increases performance throughput

         3.Decreases application latency(dormancy)

         4.Reduces cost and complexity

2.DataPower XML Security Gateway XS40

         1.Secures SOA and Web services deployments

         2.Provides comprehensive XML security

         3.Advanced XML firewall and security policy enforcement point functionality

         4.Compliant with most Web services standards

3.DataPower Integration Appliance XI50

         1.Integrates SOA and Web services deployments

         2.Transforms between disparate message formats (binary, legacy, XML, etc.)

         3.Bridges wire line transport-level protocols (HTTP, MQ, FTP, JMS, Tibco EMS, etc.)

4. DataPower Gateway Appliance XI52

        1.Any-to-Any” conversion at wire-speed

        2.Bridges multiple transport protocols        3.Mainframe integration & enablement          

Overview of  XML Accelerator XA35

• Wire speed XML/XSLT/XPath processing – Accelerates XML processing, increasing throughput and decreasing latency for XML-based applications by offloading transformation and other resource-intensive functions
• Schema Validation – Performs XML Schema validation to ensure  incoming/outgoing XML documents are legitimate and properly structured
• XML Compression, XML Caching – Reduces impact of increased XML traffic
• Innovative XML Processing Capabilities — XML Pipeline processing, dynamic content generation, data and forms processing, support for popular XSLT extensions
• SSL Termination/Acceleration – Accelerates SSL with industry-leading hardware further lessening server workload
• Easy Configuration & Administration – Support CLI and WebGUI as well as fully integrated with industry standard IDEs such as Altova XML Spy and Eclipse allowing developers to design, debug and deploy against one single XML and XSLT processor

Overview of XML Security Gateway XS40

• XML/SOAP Firewall – Filter on any content, metadata or network variables
• Data Validation – Approve incoming/outgoing XML and SOAP at wirespeed
• Field Level Security- WS-Security, encrypt & sign individual fields
• XML Web Services Access Control/AAA – SAML, LDAP, RADIUS, etc.
• Multi Step – Sophisticated multi-stage pipeline
• Web Services Management – Service Level Management, Service Virtualization, Policy Management
• Transport Layer Flexibility – HTTP, HTTPS, SSL
• Easy Configuration & Management – WebGUI, CLI, IDE and Eclipse Configuration to address broad organizational needs

Overview of Integration XI50 Appliance

• The DataPower Integration Appliance XI50 model provides transport-independent transformations between binary, flat text files and XML message formats.
• Visual tools are used to describe data formats, create mappings between different formats, and define message choreography.
• The XI50 appliance can transform binary, flat text, and other non-XML messages to help offer an innovative solution for security-rich XML enablement ,ESBs , and mainframe connectivity.
• Any-to-any transformation engine
  The XI50 model can parse and transform arbitrary binary, flat text, and XML messages, including EDI, COBOL copybook, CSV,  and ebXML.
  The technology of the DataPower appliance uses a fully declarative, metadata-based approach.
• Transport bridging
  With support for a wide array of transport protocols, the XI50 is capable of bridging request and response flows to and from protocols such as HTTP, HTTPS, MQ, SSL, IMS Connect, FTP, and more.
• Integrated message-level security
  The XI50 model includes mature message-level security and access control functionality.
  Messages can be filtered, validated, encrypted, and signed, helping to provide more secure enablement of high-value applications. Supported technologies include WS-Security, WS-Trust, SAML, and LDAP.
• Lightweight message brokering
  Sophisticated multi-step message routing, filtering, and processing
  Multiple synchronous and asynchronous transport protocols
  Detailed logging and audit trail, including non-repudiation support

Usage Scenarios for DataPower SOA Appliances

• Securing Web Services :Securely enabling access to back-end system of record for partners and customers and Protecting against XML-borne threats
• Legacy Integration :Connecting mainframe or legacy application to Web services/SOA ,XML-enabling mainframe and legacy systems.(A legacy system is an old technology application program that may or may not remain in use.)
• Hub Mediation :Efficiently transforming, routing, logging messages among applications and Web services
• Enterprise Service Bus (ESB) Deployments : Provide on- and off-ramps to ESBs, manage Web services easily through service-level management, security management, enterprise management console
• Web Portal Acceleration :Speed up rendering for dynamic content generation

IBM WEBSPHERE MESSAGE QUEUE

IBM MESSAGE QUEUE:

 Message Queue: Message queue is a middleware product that can communicate or integrate two applications by sending or receiving the data.

Message: A message is a representation of data or information exchanged between the applications.

·         Binary information

·         Text data

·         Structured data

What message contain:

·         MQ Message Description

·         Body of the Message or Message body

MQ Message Description: In message description there are different values

·         Expire date and time        

·         Message ID

·         correlation ID

·         Group ID

·         Sequence Number

·         Put date and Time

·         Application name

·         QManager name

·         Queues name

Message body: Message body can contains the data or information for the application.

METHODS OF MESSAGING:

   Two types of messaging methods are there. Those are

·         Synchronous messaging

·         Asynchronous messaging

Synchronous messaging: The sender can send a message and wait for the acknowledgement from the receiver.

Asynchronous messaging: The sender can send a message continuously without waiting for the acknowledgement from the receiver.   

TYPES OF MESSAGES:

There are four types of messages

·         Data gram

·         Request

·         Reply

·         Report

Data gram: A message cannot expect response is called data gram message.

Request message: A message that can expect a response is called request message.

Reply message: A message in response to a request message is called reply message.

Report message: Report message is  a message that tells about an occurrence or an event is called 

report message.

APPLICATION PERSPECTIVE MESSAGE TYPES:

Those are two types

·         Persistent message

·         Non Persistent message

Persistent message: A message that can recoverable when failure occurs.

Non Persistent message: A message that cannot recoverable when failure occurs.

WHAT ARE THE METHODS BY USING APPLICATION TO CONNECT MQ:

Application can connect to the MQ

1.      Binding mode

2.      External mode

Binding mode: Application and MQ should be on same server.

External mode: Application and MQ on different servers.

WHAT ARE THE MQI CALLS:

  MQI calls: Application can use MQI calls to connect to the MQ Qmanager.These are divided into two categories.

1.      Major calls

2.      minor calls

Major calls:

1.      MQCONN and MQCONNX: TO connect to the Queue Manager.

2.      MQOPEN :It is using for open a queue.

3.      MQCLOSE: It is using for to close a queue.

4.      MQDISC : It is using to end the connection to the Queue Manager.      

5.      MQPUT : It is using to put a message on a queue.

6.      MQPUT1 : it means The combination of MQOPEN , MQPUT and MQCLOSE.

7.      MQGET: To get a message from the Queue.

Minor calls:

1.      MQBEGIN: To begin a unit of work.

2.      MQCMIT: To commit a unit of work.

3.      MQSET: Can be used by application to set the some of the attribute on the queue.

4.      MQBACK: To rollback the commands for unit of work.

5.      MQINQ: To Inquire about attributes of an object.

DIFFERENCES BETWEEN MQ VERSION8 AND MQ VERSION 9.

MQ Version 8

1.       new feature introduced in v8 is apiexits  which themselves make apicalls.

2.      On unix and linux systems the object authority manager (OAM) can now use userbased authorization as well as group based authorization.

3.      In IBM V8 a new Queue Manager security parameter conauth chcklocl has been introduced.

MQ Version 9

1.      A new delivary and suport model for IBMMQ has been introduced.

From version 9 two release types will be made available

                       1. long term support release(lTS)

                      2.Continues delivery Release.

     2. In v9 WEB UI has been introduced to administer MQ.

Websphere MQ Triggering

Websphere MQ Triggering

What is Triggering:

         Triggering is a mechanism that is used by websphere MQ to automatically start applications or channels only when there are trigger messages arrived on queue. It can save system resources because an application doesn't need to be running continuously and sitting in a long running mqget call waiting for messages to appear on its input queue.

Why we go for Triggering:

In order to automate the channel and application we go for triggering.

·         In general we need to start the channel manually. I dont want manual intervention to start the channel and need not be continuously running, no need to waste the cpu utilization for the channel to be running if no messages or flowing through that channel.

·         Application don't need to be connected continuously even if messages are not coming to the queue. So to avoid such scenarios we go for application triggering.

 Types of triggering:

    There are three types of trigger

1.       Channel triggering

2.       Application Triggering

3.       Client Triggering

what is TRIGTYPE and what are the different values in TRIGTYPE?

TrigType is an attribute under transmission queue or local queue to enable triggering mechanism. There are three different values available for this attribute.

1.       FIRST: for the very first message only the trigger fires and trigger message will be generated by the queue manager.

2.       DEPTH: For depth after the depth condition satisfied then only the trigger fires.

3.       EVERY: For every message trigger fires and queue manager will generate the trigger message.

Trigger Message:

Whenever Trigger event generated  (when certain conditions are met) Trigger message will generate and this trigger message hold by initiation Queue. This trigger message is generated by the queue manager. If in case the trigger fails the message will go to dead latter queue.

Channel Triggering: When certain conditions are satisfied on transmition queue(xmitq) the trigger message will be generated by the queue manager and will plays this message on to the initiation queueu(initq), the channel initiator will be continuously monitoring this initq once trigger message generated it will intimate to the sendermca to pic the messages from xmitq and start the channel.

Syntax for channel triggering:

ALTER QLOCAL(XMITQNAME) TRIGGER TRIGTYPE (FIRST /EVERY/DEPTH) TRIGDPTH(1)TRIGDATA(SENDER CHANNELNAME)  INITQ(SYSTEM.CHANNEL.INITQ)

Note: we need to mention trigdpth value when ever we mention trig type(depth) other wise we should keep the trig depth as default.

Application Triggering: When ever certain conditions are met on the local queue the trigger message will be generated by the queue manager which will keeps on initiation queue, trigger monitor is the program which will continuously monitor the initation queue for trigger message which in turn starts an application by reading the application details from the process definition.

Syntax for application triggering:

ALTER QLOCAL(LOCAL QNAME) TRIGGER TRIGTYPE(FIRST/EVER/DEPTH) TRIGDEPTH(5) INITQ(SYSTEM.DEFAULT.INITIATION.QUEUE) PROCESS(PROCESS NAME)

DEFINE PROCESS(PROCESS NAME) APPLICID('C:\APPLICATION.EXE') APPLTYPE(WINDOWS OR UNIX)

Client Triggering: If you want to run a script on a remote machine when the queue is on the server machine , for this we have one solution here is client triggering. These means that you run a client trigger monitor on the remote machine.  when something lands on the queue on the server the client trigger monitor will run the script on the remote machine.

Setup:

On server 

1) Create a new client channel with chltype(svrconn)

2) Create a new INITQ

3) Create a process with applicid as it would be if you run the command on remote machine

4) Create a new queue with the new INITQ and Process.

Client side:

1)Set the MQ SERVER environmental variable

Syntax: MQSERVER ='CLIENT CHANNEL/TCP/IPADDRESS(PORT)

2) Check that the remote machine can talk to the server.

3) start the client trigger monitor.

Syntax: RUNMQTMC -M QMANAGERNAME -Q INITQNAME

What is Triggering:

         Triggering is a mechanism that is used by websphere MQ to automatically start applications or channels only when there are trigger messages arrived on queue. It can can save system resources because an application doesn't need to be running continuously and sitting in a long running mqget call waiting for messages to appear on its input queue.

Why we go for Triggering:

In order to automate the channel and application we go for triggering.

·         In general we need to start the channel manually. I dont want manual intervention to start the channel and need not be continuously running, no need to waste the cpu utilization for the channel to be running if no messages or flowing through that channel.

·         Application don't need to be connected continuously even if messages are not coming to the queue. So to avoid such scenarios we go for application triggering.

 Types of triggering:

    There are three types of trigger

1.       Channel triggering

2.       Application Triggering

3.       Client Triggering

what is TRIGTYPE and what are the different values in TRIGTYPE?

TrigType is an attribute under transmission queue or local queue to enable triggering mechanism. There are three different values available for this attribute.

1.       FIRST: for the very first message only the trigger fires and trigger message will be generated by the queue manager.

2.       DEPTH: For depth after the depth condition satisfied then only the trigger fires.

3.       EVERY: For every message trigger fires and queue manager will generate the trigger message.

Trigger Message:

Whenever Trigger event generated  (when certain conditions are met) Trigger message will generate and this trigger message hold by initiation Queue. This trigger message is generated by the queue manager. If in case the trigger fails the message will go to dead latter queue.

Channel Triggering: When certain conditions are satisfied on transmition queue(xmitq) the trigger message will be generated by the queue manager and will plays this message on to the initiation queueu(initq), the channel initiator will be continuously monitoring this initq once trigger message generated it will intimate to the sendermca to pic the messages from xmitq and start the channel.

Syntax for channel triggering:

ALTER QLOCAL(XMITQNAME) TRIGGER TRIGTYPE (FIRST /EVERY/DEPTH) TRIGDPTH(1)TRIGDATA(SENDER CHANNELNAME)  INITQ(SYSTEM.CHANNEL.INITQ)

Note: we need to mention trigdpth value when ever we mention trig type(depth) other wise we should keep the trig depth as default.

Application Triggering: When ever certain conditions are met on the local queue the trigger message will be generated by the queue manager which will keeps on initiation queue, trigger monitor is the program which will continuously monitor the initation queue for trigger message which in turn starts an application by reading the application details from the process definition.

Syntax for application triggering:

ALTER QLOCAL(LOCAL QNAME) TRIGGER TRIGTYPE(FIRST/EVER/DEPTH) TRIGDEPTH(5) INITQ(SYSTEM.DEFAULT.INITIATION.QUEUE) PROCESS(PROCESS NAME)

DEFINE PROCESS(PROCESS NAME) APPLICID('C:\APPLICATION.EXE') APPLTYPE(WINDOWS OR UNIX)

Client Triggering: If you want to run a script on a remote machine when the queue is on the server machine , for this we have one solution here is client triggering. These means that you run a client trigger monitor on the remote machine.  when something lands on the queue on the server the client trigger monitor will run the script on the remote machine.

Setup:

On server 

1) Create a new client channel with chltype(svrconn)

2) Create a new INITQ

3) Create a process with applicid as it would be if you run the command on remote machine

4) Create a new queue with the new INITQ and Process.

Client side:

1)Set the MQ SERVER environmental variable

Syntax: MQSERVER ='CLIENT CHANNEL/TCP/IPADDRESS(PORT)

2) Check that the remote machine can talk to the server.

3) start the client trigger monitor.

Syntax: RUNMQTMC -M QMANAGERNAME -Q INITQNAME

IBM MQ INSTALLATION PROCESS IN WINDOWS SERVER

  IBM MQ v9 INSTALLATION PROCESS:

Before installing the MQ we need to make sure the following things to be checked out

MQ packages

Client Package: Client package is software which requires by an application to connect to MQ. This package must be installed on the server from where the application is trying to connect to an MQ server. It is free of cost

Server package: Server package is software which is used for creating the object like Queue Manager, Queue, Listeners, Channels, Process. This server package is compulsory to be installed for creating any of the objects

To download the MQ Software, steps to go

• Open google and enter IBM Mq download

> Open the link and select the download button on window.

 > If you have IBM id check the box "I already have an IBM id" and continue to login.

> Those who don't have IBM id please leave check box and click on continue to create an count.

> Here fill your details and register.

> After register , login to the IBM page.

> Select the proper version and continue to download.

> After that we have to fill all the required details and click on conform

 > After that we have to fill all the required details and click on conform

> should select the DOWNLOAD USING HTTP.

Select the required version and click on i agree. then the MQ downloaded.

After download the MQ , Maintain floder information like below.

IMPORTANT FOLDERS, PATHS AND LOCATIONS

Data folderàworking files will save here

Log folderàlog info

Bin Details or Installation Path àAll executable files.

Ex:

BIN PATH: C:\Program Files (x86) (x86)\IBM\WebSphere MQ\bin

Working Directory: C:\Program Files (x86) (x86)\IBM\WebSphere MQ\QMGRs

Log Directory: C:\Program Files (x86) (x86)\IBM\WebSphere MQ\log

We need to consider the following...

1) S/W Requirements (OS Compatibility, Computer name (should not contain any spaces), IES (MQ Explorer for GUI mode))

2) H/W Requirements (disk space)

Once these are checked out we need to install the MQ Explore as below go to PREREQ folder under that Click on IES under this folder we will see the setup.exe file for Explorer.

In before unzip the Downloaded file and placed into proper location. 

Once this is done we need to install the software by using the launch pad from the main folder ,on the left hand side we do have several options  check for software requirements and then use the WebSphere installation tab to launch installation process.

After accepting the License we do have options for installing

a) COMPACT

b) TYPICAL

c) CUSTOM

Select the custom option and then select the packages whatever you required…and click install.

Note: The only the client package is required we can select only one package and then click for install.

Once complete installation is done it will ask for Domain configuration which is configuring the domain details with particular domain name, user id and password

In general these are done by Windows Admin team so we don’t require select NO option so it will stop configuring the domain configuration.

If you want domain configuration click YES and fill the below details Once this is done Installation is done

    UNDER WHICH USER ID THE MQ SOFTWARE RUNS?

Once you installed MQ software it will be running with 'mqm' group and with user id 'MUSR_MQADMIN'

If you want to see the ‘users and groups’ in Windows 7, right click on MY computer and select ‘Manage’ it will take to a windows where you can see ‘users and groups tab’

Once you installed the Software you will have the service name 'IBMMQSeries' under service tab(services.msc ) which will be started automatically by default, if you want to change it to manual we can do it.

If the service is in stopped state or not started then you will get the below error while you start to work on MQ commands.

C:\Windows\System32>strmqm QM1

AMQ7257: The MQ service must be running to perform the requested operation.

NOTE: while you are working on windows 7 OS please start the command prompt as ‘Run as Administrator’

Note: The users who are part of ‘mqm’ group will be able to run the MQ commands, creation of user id’s and adding them to ‘mqm’ group will be taken care by windows/unix admin.