Install Subversion 1.7 from wandisco repository on Debian GNU/Linux Wheezy

Debian GNU/Linux Wheezy is still using subversion 1.6.x, here there is a shellscript according the instructions given by this blogger to install subversion 1.7:

----------------------------------------------------------------------

#!/bin/bash
#http://ymartin59.free.fr/wordpress/index.php/2012/11/25/how-to-install-subversion-1-7-from-wandisco-repository-on-debian-wheezy/
apt-get install equivs

cat > libdb4.8-control-wheezy <<EOF
### Commented entries have reasonable defaults.
### Uncomment to edit them.
# Source: <source package name; defaults to package name>
Section: misc
Priority: optional
# Homepage: <enter URL here; no default>
Standards-Version: 3.9.2

Package: libdb4.8
Version: 4.8.30-fake
Maintainer: Yves Martin <guess@free.fr>
# Pre-Depends: <comma-separated list of packages>
Depends: db4.8-util
# Recommends: <comma-separated list of packages>
# Suggests: <comma-separated list of packages>
# Provides: <comma-separated list of packages>
# Replaces: <comma-separated list of packages>
Architecture: all
# Copyright: <copyright file; defaults to GPL2>
# Changelog: <changelog file; defaults to a generic changelog>
# Readme: <README.Debian file; defaults to a generic one>
# Extra-Files: <comma-separated list of additional files for the doc directory>
# Files: <pair of space-separated paths; First is file to include, second is destination>
#  <more pairs, if there's more than one file to include. Notice the starting space>
Description: Link to new package name db4.8-util
EOF

equivs-build libdb4.8-control-wheezy
apt-get install db4.8-util
dpkg -i libdb4.8_4.8.30-fake_all.deb

wget -q -O - http://opensource.wandisco.com/wandisco-debian.gpg | sudo apt-key add -
echo "deb http://opensource.wandisco.com/debian/ squeeze svn17" > /etc/apt/sources.list.d/wandisco-subversion.list
apt-get update
apt-get install subversion subversion-tools

svn help
----------------------------------------------------------------------

Enjoy!

Jenkins in Weblogic Application Server 12c

To deploy jenkins in Weblogic server 12c you need a little ajustment as it is described in "Install the Jenkins as a WAR to the Weblogic server".

Here a bash shellscript using "Here Documents" to do it faster:

---------------------------------------------------------------------------------------
#!/bin/bash
TARGET=$1

if [ -z "$TARGET" ] || [ ! -e $TARGET ]
then
        echo "I need an absolut path to the jenkins war!"
        exit 1
fi

TMPDIR=$HOME/tmp/jenkins-ci/jenkins
MYPWD=$(pwd)
rm -fr $TMPDIR
mkdir -p $TMPDIR
cd $TMPDIR
unzip $TARGET

cat > WEB-INF/weblogic.xml <<ENDOFMESSAGE
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app
    xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsdhttp://xmlns.oracle.com/weblogic/weblogic-web-apphttp://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd">
    <wls:weblogic-version>10.3.4</wls:weblogic-version>
    <wls:context-root>jenkins</wls:context-root>
    <wls:container-descriptor>
        <wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
    </wls:container-descriptor>
</wls:weblogic-web-app>
ENDOFMESSAGE

mkdir -p $MYPWD/weblogic
RESULT=$MYPWD/weblogic/jenkins.war
zip -r $RESULT *

ls -l $RESULT
---------------------------------------------------------------------------------------

 Example:

./weblogic-jenkins.sh jenkins.war

Enjoy!

Preparing a USB stick using a network installer CD for Debian Squeeze

It can not be easier!

To install Debian GNU/Linux from network using a USB stick, download an installer image from here, from here if you need some non-free firmware or from here for the freshest version available.

Insert your usb stick and identify the device using dmesg.

dmesg

.

..

...

[3848496.714205] usb 3-2: new high speed USB device using ehci_hcd and address 4
[3848496.847464] usb 3-2: New USB device found, idVendor=03f0, idProduct=5307
[3848496.847468] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[3848496.847472] usb 3-2: Product: v165w
[3848496.847475] usb 3-2: Manufacturer: HP
[3848496.847478] usb 3-2: SerialNumber: 00000000000064
[3848496.847595] usb 3-2: configuration #1 chosen from 1 choice
[3848497.230156] Initializing USB Mass Storage driver...
[3848497.230383] scsi8 : SCSI emulation for USB Mass Storage devices
[3848497.230523] usb-storage: device found at 4
[3848497.230527] usb-storage: waiting for device to settle before scanning
[3848497.230541] usbcore: registered new interface driver usb-storage
[3848497.230548] USB Mass Storage support registered.
[3848502.230522] usb-storage: device scan complete
[3848502.231119] scsi 8:0:0:0: Direct-Access     hp       v165w            0.00 PQ: 0 ANSI: 2
[3848502.233229] sd 8:0:0:0: [sdh] 7892040 512-byte logical blocks: (4.04 GB/3.76 GiB)
[3848502.233720] sd 8:0:0:0: [sdh] Write Protect is off
[3848502.233724] sd 8:0:0:0: [sdh] Mode Sense: 00 00 00 00
[3848502.233728] sd 8:0:0:0: [sdh] Assuming drive cache: write through
[3848502.236846] sd 8:0:0:0: [sdh] Assuming drive cache: write through
[3848502.236851]  sdh:
[3848502.906878] sd 8:0:0:0: [sdh] Assuming drive cache: write through
[3848502.906884] sd 8:0:0:0: [sdh] Attached SCSI removable disk

So, in my case the device is /dev/sdh:

cat firmware-6.0.4-amd64-netinst.iso > /dev/sdh
sync

That's it, just boot from the USB stick and enjoy!

JBoss Messaging Message Bridge Configuration and Weblogic

Some days ago I had to deploy a JBoss Application Server 5.1 (JBoss AS) as integration point between a Weblogic Application Server 11g (WLS) and some another rare artifacts. Just like that.

Messages sent into a first JMS queue, provided by the JBoss AS, must be consumed by a Message Driven Bean (MDB) located in the WLS and some messages must be produced into a second JMS queue. But a remote queue is not something you can inject into a EJB.

A messaging bridge had to be placed in between:

Here the messaging bridge service is provided by the integration server, in this case the JBoss AS (node B). So, the explanation is done from the integration point of view.

Step 1

In your JBoss AS, edit the file you_server_configuration/deploy/messaging/jms-ds.xml and add the following blocks of xml code to define the two bridges and the remote provider:


<connection-factories>

...

<!-- RemoteJMSProvider for WLS -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
  name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider">

    <attribute name="ProviderName">RemoteJMSProvider</attribute>
    <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
    <attribute name="FactoryRef">/SomeConnectionFactory</attribute>
    <attribute name="QueueFactoryRef">/SomeConnectionFactory</attribute>
    <attribute name="TopicFactoryRef">/SomeConnectionFactory</attribute>
    <attribute name="Properties">
       java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
       java.naming.provider.url=t3://your_ip_for_node_a:7001
       java.naming.security.authentication=none
    </attribute>
</mbean>

<mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.messaging:service=Bridge,name=IntegrationInputBridge" xmbean-dd="xmdesc/Bridge-xmbean.xml">
     <!-- The JMS provider loader that is used to lookup the source destination -->
     <depends optional-attribute-name="SourceProviderLoader">
        jboss.messaging:service=JMSProviderLoader,name=JMSProvider
     </depends>

     <!-- The JMS provider loader that is used to lookup the target destination -->
     <depends optional-attribute-name="TargetProviderLoader">
        jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider
     </depends>

      <!-- The JNDI lookup for the source destination -->
      <attribute name="SourceDestinationLookup">/queue/IntegrationInputQueue</attribute>
      <attribute name="TargetDestinationLookup">/queue/IntegrationInputQueue</attribute>
      <!-- The username to use for the source connection
      <attribute name="SourceUsername"></attribute>        -->
      <!-- The password to use for the source connection
      <attribute name="SourcePassword"></attribute>        -->
      <!-- The username to use for the target connection  
      <attribute name="TargetUsername"></attribute>        -->
      <!-- The password to use for the target connection 
      <attribute name="TargetPassword"></attribute>        -->

      <!-- Optional: The Quality Of Service mode to use, one of:
           QOS_AT_MOST_ONCE = 0;  QOS_DUPLICATES_OK = 1;  QOS_ONCE_AND_ONLY_ONCE = 2; -->
      <attribute name="QualityOfServiceMode">0</attribute>

      <!-- JMS selector to use for consuming messages from the source
      <attribute name="Selector">specify jms selector here</attribute>      -->

      <!-- The maximum number of messages to consume from the source before sending to the target -->
      <attribute name="MaxBatchSize">1</attribute>

      <!-- The maximum time to wait (in ms) before sending a batch to the target even if MaxBatchSize is not exceeded. -1 means wait forever -->
      <attribute name="MaxBatchTime">-1</attribute>

      <!-- If consuming from a durable subscription this is the subscription name
      <attribute name="SubName"></attribute>      -->
      <!-- If consuming from a durable subscription this is the client ID to use
      <attribute name="ClientID"></attribute>      -->

      <!-- The number of ms to wait between connection retrues in the event connections to source or target fail -->
      <attribute name="FailureRetryInterval">5000</attribute>

      <!-- The maximum number of connection retries to make in case of failure, before giving up
           -1 means try forever-->
      <attribute name="MaxRetries">-1</attribute>

      <!-- If true then the message id of the message before bridging will be added as a header to the message so it is available
           to the receiver. Can then be sent as correlation id to correlate in a distributed request-response -->
      <attribute name="AddMessageIDInHeader">false</attribute>
</mbean>

<mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.messaging:service=Bridge,name=IntegrationOutputBridge" xmbean-dd="xmdesc/Bridge-xmbean.xml">
     <!-- The JMS provider loader that is used to lookup the target destination -->
     <depends optional-attribute-name="TargetProviderLoader">
        jboss.messaging:service=JMSProviderLoader,name=JMSProvider
     </depends>
     <!-- The JMS provider loader that is used to lookup the source destination -->
     <depends optional-attribute-name="SourceProviderLoader">
        jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider
     </depends>
      <!-- The JNDI lookup for the source destination -->
      <attribute name="SourceDestinationLookup">/queue/IntegrationOutputQueue</attribute>
      <attribute name="TargetDestinationLookup">/queue/IntegrationOutputQueue</attribute>
      <!-- The username to use for the source connection
      <attribute name="SourceUsername"></attribute>        -->
      <!-- The password to use for the source connection
      <attribute name="SourcePassword"></attribute>        -->
      <!-- The username to use for the target connection  
      <attribute name="TargetUsername"></attribute>        -->
      <!-- The password to use for the target connection 
      <attribute name="TargetPassword"></attribute>        -->
      <!-- Optional: The Quality Of Service mode to use, one of:
           QOS_AT_MOST_ONCE = 0;  QOS_DUPLICATES_OK = 1;  QOS_ONCE_AND_ONLY_ONCE = 2; -->
      <attribute name="QualityOfServiceMode">0</attribute>
      <!-- JMS selector to use for consuming messages from the source
      <attribute name="Selector">specify jms selector here</attribute>      -->
      <!-- The maximum number of messages to consume from the source before sending to the target -->
      <attribute name="MaxBatchSize">1</attribute>
      <!-- The maximum time to wait (in ms) before sending a batch to the target even if MaxBatchSize is not exceeded. -1 means wait forever -->
      <attribute name="MaxBatchTime">-1</attribute>
      <!-- If consuming from a durable subscription this is the subscription name
      <attribute name="SubName"></attribute>      -->
      <!-- If consuming from a durable subscription this is the client ID to use
      <attribute name="ClientID"></attribute>      -->
      <!-- The number of ms to wait between connection retrues in the event connections to source or target fail -->
      <attribute name="FailureRetryInterval">5000</attribute>
      <!-- The maximum number of connection retries to make in case of failure, before giving up
           -1 means try forever-->
      <attribute name="MaxRetries">-1</attribute>
      <!-- If true then the message id of the message before bridging will be added as a header to the message so it is available
           to the receiver. Can then be sent as correlation id to correlate in a distributed request-response -->
      <attribute name="AddMessageIDInHeader">false</attribute>
</mbean>
...
</connection-factories>

The first mbean block declares a RemoteJMSProvider which is the responsible for the remote connection with JMS container at the WLS.

The second mbean block declares a bridge that will send forward to WLS any message incoming into /queue/IntegrationInputQueue in the JBoss AS.

The third mbean block declares a bridge that will bring backward to JBoss AS any message incoming into /queue/IntegrationOutputQueue in the WLS.

Step 2: Create two queues at the WLS to replicate the other two at the JBoss AS.

/queue/IntegrationInputQueue

/queue/IntegrationOutputQueue

Step 3:  Copy the client jar to create connections from the WLS.

$JAVA_HOME/server/yourServerConfiguration/lib/wlfullclient.jar

Step 4: Of course, you need to enable the ports the servers need to traffic on, check your firewall.

Be advice, the serialization between slightly different java virtual machines may be a "real pain in the keyboard" sometimes. If a obscure RuntimeException is thrown when the serialization is being done, I suggest you to check the JVM's versions, otherwise you are playing with fire :-)
But, if you have a homogeneous production environment you probably won't have any problems.

Excuse my written english, enjoy!

Managing the Cisco SGE2000 switch from Linux remotely

Today I had to access a new switch fresh out the box to manage for the first time, the Cisco SGE2000 24-port Gigabit Switch!

To manage the switch remotely I chose to plug a second network interface card (NIC) in a general purpose linux server with Debian GNU/Linux. Here is the previous network configuration:

# cat /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo eth2
iface lo inet loopback

# The primary network interface
allow-hotplug eth2
iface eth2 inet static
        address 192.168.24.111
        netmask 255.255.255.0
        network 192.168.24.0
        post-up iptables-restore < /etc/iptables.up.rules

In my network the gateway is located at 192.168.24.1.
Why using the eth2 for the default network access? Well, I needed the server to have a wake-on-lan capable NIC.

As indicated in the the quick start guide, to configure the switch over IP with Web GUI you should connect a PC to any of the non-stacking ethernet ports with an Ethernet cable.

"The default static IP address is 192.168.1.254 and the default management VLAN for the static IP address is VLAN 1. The default user name is admin and the default password is admin."

Well, if you have a second NIC available in a linux box connected to the switch you just can use it to manage the switch. Remember that the first NIC is need to access remotely the linux box as usual. You don't just have to be physically there :-) Just plug the cable and do it from your desktop (may be from your home?).

The new network configuration is:

# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo eth2
iface lo inet loopback

#Switch management

auto eth0
allow-hotplug eth0
iface eth0 inet static
        address 192.168.1.111
        netmask 255.255.255.0
        network 192.168.1.0
        gateteway 192.168.1.254

# The primary network interface
allow-hotplug eth2
iface eth2 inet static
        address 192.168.24.111
        netmask 255.255.255.0
        network 192.168.24.0
        post-up iptables-restore < /etc/iptables.up.rules

The NIC that I will use to manage the switch is eth0 (I use the eth2 as the default because the wake-on-lan feature), the network and the gateway indicated here are needed because because we are avoiding to stand in front of the switch with a laptop connected directly. We talk now talk with switch directly.

The network configuration is now:

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1c:c0:a1:7b:df 
          inet addr:192.168.1.111  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21c:c0ff:fea1:7bdf/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:719 errors:0 dropped:0 overruns:0 frame:0
          TX packets:401 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:369094 (360.4 KiB)  TX bytes:37445 (36.5 KiB)
          Memory:e3200000-e3220000

eth2      Link encap:Ethernet  HWaddr 5c:d9:98:9e:ab:7a 
          inet addr:192.168.24.111  Bcast:192.168.24.255  Mask:255.255.255.0
          inet6 addr: fe80::5ed9:98ff:fe9e:ab7a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:34219 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15991 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10273485 (9.7 MiB)  TX bytes:3165535 (3.0 MiB)
          Interrupt:18 Base address:0x4000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3742 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3742 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:18011813 (17.1 MiB)  TX bytes:18011813 (17.1 MiB)

The route table is now:

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.24.0    0.0.0.0         255.255.255.0   U     0      0        0 eth2
0.0.0.0         192.168.24.1    0.0.0.0         UG    0      0        0 eth2

And now we access the switch's web interface from the linux box. In my case I just started a vncserver (local port forwarding with ssh) and login remotely from my home :-)

We can access the telnet interface as well:

$ telnet 192.168.1.254

Now you may need this administration guide.

Enjoy!