[DEPRECATED] CentOS 6: Install MongoDB Java REST server

Verisons

CentOS 6.4
Oracle Java 1.6 JDK
MongoDB 2.4

Prerequisites

Install

1. Download, extract tar and mv to /usr/lib

wget http://commondatastorage.googleapis.com/andreidata/mongoser.tar.gz
tar xvf mongoser.tar.gz
sudo mv mongoser /usr/lib

wget http://commondatastorage.googleapis.com/andreidata/mongoser.tar.gz

tar xvf mongoser.tar.gz

sudo mv mongoser /usr/lib

Install as a service

1. Edit /etc/init.d/mongoser

#!/bin/sh
#
# chkconfig: 2345 80 80
#
# Bash script to run mongoser.sh as a service
#

# Note: Normal env variables are discarded by service. So must export JAVA_HOME here, see http://serverfault.com/questions/374404/service-command-and-environment-variables
export JAVA_HOME=/usr/java/latest

MONGOSER_HOME=/usr/lib/mongoser
MONGOSER_DAEMON=bin/mongoser.sh
MONGOSER_USER=root
START_OPTIONS=start
STOP_OPTIONS=stop

start() {
    echo "Starting Mongoser Java REST for MongoDB..."
    su --preserve-environment $MONGOSER_USER -c "cd $MONGOSER_HOME && $MONGOSER_DAEMON $START_OPTIONS"
    return 0
}

stop() {
    echo "Stopping Mongoser Java REST for MongoDB..."
    su --preserve-environment $MONGOSER_USER -c "cd $MONGOSER_HOME && $MONGOSER_DAEMON $STOP_OPTIONS"
    return 0
}

case "$1" in
  start)
    start
    ;;
  stop)
    stop
      ;;
  restart)
    stop
    start
    ;;
  *)
  echo $"Usage: $0 {start|stop|restart}"
  exit 1
esac

exit $?

#!/bin/sh

# chkconfig: 2345 80 80

# Bash script to run mongoser.sh as a service

# Note: Normal env variables are discarded by service. So must export JAVA_HOME here, see http://serverfault.com/questions/374404/service-command-and-environment-variables

export JAVA_HOME=/usr/java/latest

MONGOSER_HOME=/usr/lib/mongoser

MONGOSER_DAEMON=bin/mongoser.sh

MONGOSER_USER=root

START_OPTIONS=start

STOP_OPTIONS=stop

start() {

echo "Starting Mongoser Java REST for MongoDB..."

su --preserve-environment $MONGOSER_USER -c "cd $MONGOSER_HOME && $MONGOSER_DAEMON $START_OPTIONS"

return 0

}

stop() {

echo "Stopping Mongoser Java REST for MongoDB..."

su --preserve-environment $MONGOSER_USER -c "cd $MONGOSER_HOME && $MONGOSER_DAEMON $STOP_OPTIONS"

return 0

}

case "$1" in

start)

start

;;

stop)

stop

;;

restart)

stop

start

;;

echo $"Usage: $0 {start|stop|restart}"

exit 1

esac

exit $?

Note: the script hard codes JAVA_HOME, but this could be deferred to the /etc/sysconfig/mongoser script (which you must create) if desired. Note that the normal /etc/profile.sh is *not* run for services.
2. Make it executable

sudo chmod +x /etc/init.d/mongoser

1	sudo chmod +x /etc/init.d/mongoser

3. Start service

sudo service mongoser start

1	sudo service mongoser start

4. Start service on boot

sudo chkconfig mongoser on

1	sudo chkconfig mongoser on

Test

1. Get a list of databases

curl -i "http://localhost:8081/database"

1	curl -i "http://localhost:8081/database"

Output:

HTTP/1.1 200 OK
Cache-Control: no-cache,no-store,must-revalidate
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked

["local"]

HTTP/1.1 200 OK

Cache-Control: no-cache,no-store,must-revalidate

Content-Type: application/json;charset=UTF-8

Transfer-Encoding: chunked

["local"]

Source

https://sites.google.com/site/mongodbjavarestserver/home

CentOS 6: Open a Port for iptables

2 Replies

Verisons

CentOS 6.5

Configure

Edit /etc/sysconfig/iptables and add the following before COMMIT

Typical /etc/sysconfig/iptables:

# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT

# Firewall configuration written by system-config-firewall

# Manual customization of this file is not recommended.

*filter

:INPUT ACCEPT [0:0]

:FORWARD ACCEPT [0:0]

:OUTPUT ACCEPT [0:0]

-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

-A INPUT -p icmp -j ACCEPT

-A INPUT -i lo -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT

-A INPUT -j REJECT --reject-with icmp-host-prohibited

-A FORWARD -j REJECT --reject-with icmp-host-prohibited

COMMIT

If opening TCP port, add the following line above the first reject statement:

Default

-A INPUT -m state --state NEW -m tcp -p tcp --dport <port> -j ACCEPT

1

-A INPUT -m state --state NEW -m tcp -p tcp --dport <port> -j ACCEPT

Note
if tcp or udp wasn’t specified assume tcp

If udp, instead add the following line above the first reject statement:

-A INPUT -m state --state NEW -m udp -p udp --dport <port> -j ACCEPT

1	-A INPUT -m state --state NEW -m udp -p udp --dport <port> -j ACCEPT

Example: Open port 666 for tcp

# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 666 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT

# Firewall configuration written by system-config-firewall

# Manual customization of this file is not recommended.

*filter

:INPUT ACCEPT [0:0]

:FORWARD ACCEPT [0:0]

:OUTPUT ACCEPT [0:0]

-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

-A INPUT -p icmp -j ACCEPT

-A INPUT -i lo -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 666 -j ACCEPT

-A INPUT -j REJECT --reject-with icmp-host-prohibited

-A FORWARD -j REJECT --reject-with icmp-host-prohibited

COMMIT

Restart iptables

Shell

service iptables restart

1

service iptables restart

Test from remote machine

Note	replace $HOSTNAME and $PORT below

telnet $HOSTNAME $PORT

1	telnet $HOSTNAME $PORT

CentOS 6: Install MongoDB

1 Reply

Versions

CentOS 6.5
MongoDB 2.4.10

Install

Edit /etc/yum.repos.d/10gen.repo

Default

[10gen] name=10gen Repository baseurl=http://downloads-distro.mongodb.org/repo/redhat/os/x86_64 gpgcheck=0

1
2
3
4

[10gen]
name=10gen Repository
baseurl=http://downloads-distro.mongodb.org/repo/redhat/os/x86_64
gpgcheck=0
Install

Shell

sudo yum install mongo-10gen mongo-10gen-server

1

sudo yum install mongo-10gen mongo-10gen-server

Configure

Start service

Shell

sudo service mongod start

1

sudo service mongod start
Start on boot

Shell

sudo chkconfig mongod on

1

sudo chkconfig mongod on

Test

$ mongo
MongoDB shell version: 2.4.0
> use test
switched to db test
> db.foo.find()
> db.foo.save({a: 1})
> db.foo.find()
{ "_id" : ObjectId("514cd798c59449cc1f1344d3"), "a" : 1 }
> db.foo.update({a: 1}, {a: 5})
> db.foo.find()
{ "_id" : ObjectId("514cd798c59449cc1f1344d3"), "a" : 5 }
> db.foo.remove({a: 5})
> db.foo.find()

$ mongo

MongoDB shell version: 2.4.0

> use test

switched to db test

> db.foo.find()

> db.foo.save({a: 1})

> db.foo.find()

{ "_id" : ObjectId("514cd798c59449cc1f1344d3"), "a" : 1 }

> db.foo.update({a: 1}, {a: 5})

> db.foo.find()

{ "_id" : ObjectId("514cd798c59449cc1f1344d3"), "a" : 5 }

> db.foo.remove({a: 5})

> db.foo.find()

Optional: Open firewall port

Open port 27017 for mongodb See CentOS 6: Open a port for iptables

Sources

[DEPRECATED] CentOS 6: Install Hadoop from Apache Bigtop

3 Replies

WARNING

This guide is a work-in-progress and currently does not result in a fully working Hadoop. Please see CentOS 6: Install Single-node Hadoop from Cloudera CDH

Overview

Guide for setting up a single-node Hadoop on CentOS using the Apache Bigtop repo.

Versions

CentOS 6.3
Oracle Java JDK 1.6
Apache BigTop 0.5.0
Hadoop 2.0.2-alpha

Prerequisties

Install Oracle JDK

Install

1. Download the yum repo file:

sudo wget -O /etc/yum.repos.d/bigtop.repo http://www.apache.org/dist/bigtop/bigtop-0.5.0/repos/centos6/bigtop.repo

1	sudo wget -O /etc/yum.repos.d/bigtop.repo http://www.apache.org/dist/bigtop/bigtop-0.5.0/repos/centos6/bigtop.repo

2. Install

sudo yum install hadoop*

1	sudo yum install hadoop*

Configure

Separate where the namenode and datanode store their files

1. Edit /etc/hadoop/conf/hdfs-site.xml and change the following properties to the listing below:

dfs.namenode.name.dir
dfs.namenode.checkpoint.dir
dfs.datanode.data.dir

...
  <property>
     <name>dfs.namenode.name.dir</name>
     <value>file:///var/lib/hadoop-hdfs/namenode/${user.name}/dfs/name</value>
  </property>
  <property>
     <name>dfs.namenode.checkpoint.dir</name>
     <value>file:///var/lib/hadoop-hdfs/namenode/${user.name}/dfs/namesecondary\</value>
  </property>
  <property>
     <name>dfs.datanode.data.dir</name>
     <value>file:///var/lib/hadoop-hdfs/datanode/${user.name}/dfs/data</value>
  </property>
...

...

<name>dfs.namenode.name.dir</name>

<value>file:///var/lib/hadoop-hdfs/namenode/${user.name}/dfs/name</value>

</property>

<name>dfs.namenode.checkpoint.dir</name>

<value>file:///var/lib/hadoop-hdfs/namenode/${user.name}/dfs/namesecondary\</value>

</property>

<name>dfs.datanode.data.dir</name>

<value>file:///var/lib/hadoop-hdfs/datanode/${user.name}/dfs/data</value>

</property>

...

Note: this step is not part of the official Apache BigTop instructions, but was required to avoid errors when running a datanode on the same machine as the namenode.

2. Format the name node

sudo -u hdfs hadoop namenode -format

1	sudo -u hdfs hadoop namenode -format

Output:

...
13/03/18 03:26:48 INFO namenode.FSImage: Image file of size 119 saved in 0 seconds.
13/03/18 03:26:48 INFO namenode.NNStorageRetentionManager: Going to retain 1 images with txid >= 0
13/03/18 03:26:48 INFO namenode.FileJournalManager: Purging logs older than 0
13/03/18 03:26:48 INFO util.ExitUtil: Exiting with status 0
13/03/18 03:26:48 INFO namenode.NameNode: SHUTDOWN_MSG: 
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at localhost.localdomain/127.0.0.1
************************************************************/

...

13/03/18 03:26:48 INFO namenode.FSImage: Image file of size 119 saved in 0 seconds.

13/03/18 03:26:48 INFO namenode.NNStorageRetentionManager: Going to retain 1 images with txid >= 0

13/03/18 03:26:48 INFO namenode.FileJournalManager: Purging logs older than 0

13/03/18 03:26:48 INFO util.ExitUtil: Exiting with status 0

13/03/18 03:26:48 INFO namenode.NameNode: SHUTDOWN_MSG:

/************************************************************

SHUTDOWN_MSG: Shutting down NameNode at localhost.localdomain/127.0.0.1

************************************************************/

Note: formatting the datanode is not required, *however* if you have a previous install, you may have to to remove /var/lib/hadoop-hdfs/datanode to clear locks

3. Start hadoop namenode and datanode

sudo service hadoop-hdfs-namenode start
sudo service hadoop-hdfs-datanode start
sudo service hadoop-httpfs start
sudo service hadoop-mapreduce-historyserver start
sudo service hadoop-yarn-nodemanager start
sudo service hadoop-yarn-proxyserver start
sudo service hadoop-yarn-resourcemanager start

sudo service hadoop-hdfs-namenode start

sudo service hadoop-hdfs-datanode start

sudo service hadoop-httpfs start

sudo service hadoop-mapreduce-historyserver start

sudo service hadoop-yarn-nodemanager start

sudo service hadoop-yarn-proxyserver start

sudo service hadoop-yarn-resourcemanager start

TODO: figure out why hadoop-hdfs-zkfc doesn’t start
4. Start services on boot

sudo chkconfig hadoop-hdfs-namenode on
sudo chkconfig hadoop-hdfs-datanode on
sudo chkconfig hadoop-httpfs on
sudo chkconfig hadoop-mapreduce-historyserver on
sudo chkconfig hadoop-yarn-nodemanager on
sudo chkconfig hadoop-yarn-proxyserver on
sudo chkconfig hadoop-yarn-resourcemanager on

sudo chkconfig hadoop-hdfs-namenode on

sudo chkconfig hadoop-hdfs-datanode on

sudo chkconfig hadoop-httpfs on

sudo chkconfig hadoop-mapreduce-historyserver on

sudo chkconfig hadoop-yarn-nodemanager on

sudo chkconfig hadoop-yarn-proxyserver on

sudo chkconfig hadoop-yarn-resourcemanager on

5. Optional: Create a home directory on the hdfs

sudo -u hdfs hadoop fs -mkdir /user
sudo -u hdfs hadoop fs -mkdir /user/$USER
sudo -u hdfs hadoop fs -chown $USER /user/$USER

sudo -u hdfs hadoop fs -mkdir /user

sudo -u hdfs hadoop fs -mkdir /user/$USER

sudo -u hdfs hadoop fs -chown $USER /user/$USER

6. Edit /etc/profile.d/hadoop.sh

export HADOOP_HOME=/usr/lib/hadoop
export HADOOP_VERSION=2.0.2-alpha

1 2	export HADOOP_HOME=/usr/lib/hadoop export HADOOP_VERSION=2.0.2-alpha

7. Load into session

source /etc/profile.d/hadoop.sh

1	source /etc/profile.d/hadoop.sh

Test

1. Download the examples (they are missing 2.0.2-alpha for some reason)

sudo wget -O /usr/lib/hadoop/hadoop-examples.jar http://repo1.maven.org/maven2/org/apache/hadoop/hadoop-mapreduce-examples/2.0.3-alpha/hadoop-mapreduce-examples-2.0.3-alpha.jar

1	sudo wget -O /usr/lib/hadoop/hadoop-examples.jar http://repo1.maven.org/maven2/org/apache/hadoop/hadoop-mapreduce-examples/2.0.3-alpha/hadoop-mapreduce-examples-2.0.3-alpha.jar

2. Get a directory listing from hadoop hdfs

sudo -u hdfs hadoop fs -lsr /

1	sudo -u hdfs hadoop fs -lsr /

3. Run one of the examples

sudo -u hdfs hadoop jar /usr/lib/hadoop/hadoop-examples.jar pi 10 1000

1	sudo -u hdfs hadoop jar /usr/lib/hadoop/hadoop-examples.jar pi 10 1000

TODO: while the cluster appears to be working, this example hangs. :[

4. Navigate browser to http://<hostname>:50070

5. Click on “Live Nodes”

Sources

https://cwiki.apache.org/BIGTOP/how-to-install-hadoop-distribution-from-bigtop.html

[DEPRECATED] CentOS 6: Install wso2server.sh as a service that starts on boot

Leave a reply

Versions

CentOS 6.3
Oracle JDK 1.6

Configure

Note: Replace <product> with the abbreviated name of the WSO2 product (API Manager = ‘am’, Data Services Server = ‘dss’, etc) and replace <version> with the version number (’1.3.1′, ’4.0.6′, etc)

1. Edit /etc/init.d/wso2<product>

#!/bin/sh
#
# chkconfig: 2345 80 80
#
# Bash script to run wso2server.sh as a service
#

# Note: Normal env variables are discarded by service. So must export JAVA_HOME here, see http://serverfault.com/questions/374404/service-command-and-environment-variables
export JAVA_HOME=/usr/java/latest

WSO2_HOME=/usr/lib/<wso2 product>
WSO2_DAEMON=bin/wso2server.sh
WSO2_USER=root
START_OPTIONS=start
STOP_OPTIONS=stop

start() {
    echo "Starting WSO2 <product>..."
    su --preserve-environment $WSO2_USER -c "cd $WSO2_HOME && $WSO2_DAEMON $START_OPTIONS"
    return 0
}

stop() {
    echo "Stopping WSO2 <product>..."
    su --preserve-environment $WSO2_USER -c "cd $WSO2_HOME && $WSO2_DAEMON $STOP_OPTIONS"
    return 0
}

case "$1" in
  start)
    start
    ;;
  stop)
    stop
      ;;
  restart)
    stop
    start
    ;;
  *)
  echo $"Usage: $0 {start|stop|restart}"
  exit 1
esac

exit $?

#!/bin/sh

# chkconfig: 2345 80 80

# Bash script to run wso2server.sh as a service

# Note: Normal env variables are discarded by service. So must export JAVA_HOME here, see http://serverfault.com/questions/374404/service-command-and-environment-variables

export JAVA_HOME=/usr/java/latest

WSO2_HOME=/usr/lib/<wso2 product>

WSO2_DAEMON=bin/wso2server.sh

WSO2_USER=root

START_OPTIONS=start

STOP_OPTIONS=stop

start() {

echo "Starting WSO2 <product>..."

su --preserve-environment $WSO2_USER -c "cd $WSO2_HOME && $WSO2_DAEMON $START_OPTIONS"

return 0

}

stop() {

echo "Stopping WSO2 <product>..."

su --preserve-environment $WSO2_USER -c "cd $WSO2_HOME && $WSO2_DAEMON $STOP_OPTIONS"

return 0

}

case "$1" in

start)

start

;;

stop)

stop

;;

restart)

stop

start

;;

echo $"Usage: $0 {start|stop|restart}"

exit 1

esac

exit $?

Note: the script hard codes JAVA_HOME, but this can be deferred to the /etc/sysconfig/wso2<product> script (which you must create) if desired. Note that the normal /etc/profile.sh is *not* run for services.
TODO: find better way of setting JAVA_HOME, can’t execute /etc/profile or /etc/profile.d/java.sh directly

2. Make it executable

sudo chmod +x /etc/init.d/wso2<product>

1	sudo chmod +x /etc/init.d/wso2<product>

2. Start service on boot

sudo chkconfig wso2<product> on

1	sudo chkconfig wso2<product> on

Verify

1. Start service

sudo service wso2<product> start

1	sudo service wso2<product> start

Source

http://stackoverflow.com/questions/12596791/carbon-4-0-1-bam-2-0-as-a-linux-daemon

[DEPRECATED] WSO2: Use LDAP as the Carbon user-store for any WSO2 product

Leave a reply

Tested Products

WSO2 Data Services Server 3.0.1
WSO2 API Manager 1.3.1

Overview

All WSO2 Carbon-based products can be configured to work with LDAP simply by changing the configuration files. Out of the box Carbon uses one H2 database as a user-store that stores usernames, passwords, etc and another H2 database to store roles and permissions. This guide is for replacing the first database with LDAP. This configuration has been tested with both the WSO2 API Manager and WOS2 Data Services Server.

1. Import LDAP server PEM file into Java trust store

sudo keytool -import -v -trustcacerts -alias <alias> -file <path/to/pem/file> -keystore <path/to/carbon/truststore> -storepass <truststore-password>

1	sudo keytool -import -v -trustcacerts -alias <alias> -file <path/to/pem/file> -keystore <path/to/carbon/truststore> -storepass <truststore-password>

Default Carbon trust store: /repository/resources/security/client-truststore.jks
Defatul Carbon trust store password: wso2carbon

2. Edit <carbon-home>/repository/conf/user-mgt.xml

<UserManager>
  <Realm>
    <Configuration>
      <AdminRole>admin</AdminRole>
        <AdminUser>
          <UserName>LDAP_admin</UserName>
          <Password>not_used</Password>
        </AdminUser>
        <EveryOneRoleName>everyone</EveryOneRoleName>
        <!-- By default users in thsi role sees the registry root -->
        <Property name="dataSource">jdbc/WSO2CarbonDB</Property>
        <Property name="MultiTenantRealmConfigBuilder">org.wso2.carbon.user.core.config.multitenancy.SimpleRealmConfigBuilder</Property>
    </Configuration>
    <!-- Active directory configuration follows -->
   <UserStoreManager class="org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager">
     <Property name="ConnectionURL">ldap://&lthostname>:389</Property>
     <Property name="ConnectionName">cn=LDAP_search,ou=Users Service Accounts,dc=lancegatlin,dc=org</Property>
     <Property name="ConnectionPassword">XXXXXX</Property>
     <Property name="UserSearchBase">dc=lancegatlin,dc=org</Property>
     <Property name="UserNameListFilter">(objectClass=person)</Property>
     <Property name="UserNameAttribute">sAMAccountName</Property>
     <Property name="UserEntryObjectClass">person</Property>
     <Property name="UserNameSearchFilter">(&(objectClass=person)(sAMAccountName=?))</Property>
     <Property name="GroupEntryObjectClass">group</Property>
     <Property name="ReadLDAPGroups">false</Property>
     <Property name="GroupSearchBase">cn=users</Property>
     <Property name="GroupNameSearchFilter">(objectClass=group)</Property>
     <Property name="GroupNameAttribute">cn</Property>
     <Property name="MembershipAttribute">member</Property>
     <Property name="Referral">follow</Property>
   </UserStoreManager>
   <AuthorizationManager class="org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager">
     <Property name="AdminRoleManagementPermissions">/permission</Property>
   </AuthorizationManager>
  </Realm>
</UserManager>

<Realm>

<AdminRole>admin</AdminRole>

<UserName>LDAP_admin</UserName>

</AdminUser>

<EveryOneRoleName>everyone</EveryOneRoleName>

<Property name="dataSource">jdbc/WSO2CarbonDB</Property>

<Property name="MultiTenantRealmConfigBuilder">org.wso2.carbon.user.core.config.multitenancy.SimpleRealmConfigBuilder</Property>

</Configuration>

<Property name="ConnectionURL">ldap://&lthostname>:389</Property>

<Property name="ConnectionName">cn=LDAP_search,ou=Users Service Accounts,dc=lancegatlin,dc=org</Property>

<Property name="ConnectionPassword">XXXXXX</Property>

<Property name="UserSearchBase">dc=lancegatlin,dc=org</Property>

<Property name="UserNameListFilter">(objectClass=person)</Property>

<Property name="UserNameAttribute">sAMAccountName</Property>

<Property name="UserEntryObjectClass">person</Property>

<Property name="UserNameSearchFilter">(&(objectClass=person)(sAMAccountName=?))</Property>

<Property name="GroupEntryObjectClass">group</Property>

<Property name="ReadLDAPGroups">false</Property>

<Property name="GroupSearchBase">cn=users</Property>

<Property name="GroupNameSearchFilter">(objectClass=group)</Property>

<Property name="MembershipAttribute">member</Property>

<Property name="Referral">follow</Property>

</UserStoreManager>

<Property name="AdminRoleManagementPermissions">/permission</Property>

</AuthorizationManager>

</Realm>

</UserManager>

Note1: The password field /UserManager/Realm/Configuration/AdminRole/AdminUser/Password has no effect since the user-store is external and pre-configured.
Note2: The admin user specified at /UserManager/Realm/Configuration/AdminRole/AdminUser must be the first account to log in. Other users will not be able to log in until they are assigned a WSO2 role that has authentication privileges.
Note3: The connection name must exist in the UserSearchBase.
Note4: The user specified by /UserManager/Realm/Configuration/UserStoreManager/Property[@name="ConnectionName"] does not need to be the LDAP admin. However, it must have sufficient privileges to search all accounts that need to be authenticated.
Note5: /UserManager/Realm/Configuration/UserStoreManager/Property[@name="ReadLDAPGroups"] determines if Carbon will retain its own roles or use the LDAP server’s groups.
3. Change default admin account for Carbon applications
Note1: the file will vary depending on the WSO2 product being configured
Note2: not all WSO2 products require this (DSS does not)

API Manager

Set the username at the following XPaths:

/APIManager/AuthManager/Username/text()
/APIManager/APIGateway/Username/text()
/APIManager/APIKeyManager/Username/text()

Set the password at the following XPaths:

/APIManager/AuthManager/Password/text()
/APIManager/APIGateway/Password/text()
/APIManager/APIKeyManager/Password/text()

Sources

CentOS 6: Clear the yum cache

Leave a reply

Versions

CentOS 6.3

Overview

Ran into problems tonight after working installs of Hadoop of different versions where the yum installer would try to download the incorrect version. Required cleaning yum’s caches AND manually deleting the yum cache for the repo in /var/cache/yum.

Guide

Remove the repo

Note
replace $REPONAME below with the name of the repo to clear

Shell

sudo rm /etc/yum.repos.d/$REPONAME.repo

1

sudo rm /etc/yum.repos.d/$REPONAME.repo
Clean all

Shell

sudo yum clean all

1

sudo yum clean all
Delete the yum cache for the repo

Shell

sudo rm -rf /var/cache/yum/x86_64/6/$REPONAME

1

sudo rm -rf /var/cache/yum/x86_64/6/$REPONAME

Sources

http://www.centos.org/docs/5/html/yum/sn-yum-maintenance.html

Linux: Search and replace in files

Leave a reply

Overview

Just a quick recipe for performing search & replace on many files at once.

Recipe

Note	Replace $NAME with find match specifier, e.g. “*.php” Replace $SEARCH_LITERAL and $REPLACE_LITERAL with unquoted search/replace strings Search/replace strings must escape forward-slash(/) with back-slash(\), e.g. http:\/\/asdf.com

Recipe

find . -name $NAME -print | xargs sed -i 's/$SEARCH_LITERAL/$REPLACE_LITERAL/g'

1	find . -name $NAME -print \| xargs sed -i 's/$SEARCH_LITERAL/$REPLACE_LITERAL/g'

Example to perform replace all occurrences of foo with bar in all php files

find . -name "*.php" -print | xargs sed -i 's/foo/bar/g'

1	find . -name "*.php" -print \| xargs sed -i 's/foo/bar/g'

Source

http://rushi.wordpress.com/2008/08/05/find-replace-across-multiple-files-in-linux/

Linux: Test a SOAP web service using curl

4 Replies

Curl is a linux command-line HTTP tool.

Sample SOAP Message:

<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
  <soapenv:Body>
    <ns0:some_operation xmlns:ns0="http://some_ns_uri"/>
  </soapenv:Body>
</soapenv:Envelope>

<?xml version='1.0' encoding='utf-8'?>

<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">

<soapenv:Body>

<ns0:some_operation xmlns:ns0="http://some_ns_uri"/>

</soapenv:Body>

</soapenv:Envelope>

Sample curl command to transmit SOAP message to a SOAP service (with –data curl will automatically POST):

Note	replace $HOSTNAME,$PORT and $SOMEPATH below

curl --header "content-type: text/soap+xml; charset=utf-8"--data @sample.xml http://$HOSTNAME:$PORT/$SOMEPATH

1	curl --header "content-type: text/soap+xml; charset=utf-8"--data @sample.xml http://$HOSTNAME:$PORT/$SOMEPATH

SBT: Standard build.sbt for Scala

Leave a reply

Version

Scala 2.11.0

A basic build.sbt template:

Note

replace XXX below

scalaVersion := "2.11.0"

organization := "org.XXX.XXX"

name := "XXX"

version := "1.0-SNAPSHOT"

scalacOptions ++= Seq("-feature","-unchecked", "-deprecation")

libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.2.0" % "test"

scalaVersion := "2.11.0"

organization := "org.XXX.XXX"

name := "XXX"

version := "1.0-SNAPSHOT"

scalacOptions ++= Seq("-feature","-unchecked", "-deprecation")

libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.2.0" % "test"

Example:

scalaVersion := "2.11.0"

organization := "org.lancegatlin"

name := "myproject"

version := "1.0-SNAPSHOT"

scalacOptions ++= Seq("-feature","-unchecked", "-deprecation")

libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.2.0" % "test"

scalaVersion := "2.11.0"

organization := "org.lancegatlin"

name := "myproject"

version := "1.0-SNAPSHOT"

scalacOptions ++= Seq("-feature","-unchecked", "-deprecation")

libraryDependencies += "org.scalatest" % "scalatest_2.11" % "2.2.0" % "test"