Yes this is a bit of a tangent from my usual posts, but I like to geek out as much as the next guy, write some code, and deploy it to various Application servers.

I, as I suspect many programmers do, tend to develop my applications within Tomcat then build releases for other platforms such as WebSphere or Weblogic.   In doing so, I have come to the pretty obvious conclusion that it’s a good idea to use a Datasource references within my deployment descriptors, and allow the deployment managers to configure the AppServers for the given resources at deployment time. Over the last few days I have been struggling with how to properly configure a datasource within WebSphere and use the proper naming string within my hibernate.cfg.xml files.  I thought I would share my configuration steps in hopes that no one else has to go through this.

First You have to setup a JDBC Provider.  A JDBC provider is a JDBC driver that you can then use to connect to a database using a data source that you setup later in this example.

From the Administrative console, Open up the Resources pane, then expand JDBC.  Select JDBC Providers.

Figure 1. Depending on your scope selection, this screen shows all of the providers you have set up on your Websphere Server.

Select the Scope that you want this resource to be available at. Cell will make this resource available to all of the managed nodes and servers, but you can also make this resource available at the node or the server level.

Select New.

Figure 2. Set up your new resource.

Database Type: User Defined

Implementation Class Name: com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource

Name: That’s up to you.

Select Next, and setup your classpath to your mysql driver.

Figure 3. Setup Class Path

Hit Next then Finish.  Don’t forget to Save this setup to the master configuration.

Under the JDBC node, Select Data Providers.

Figure 4. Data Sources List

Select New.

Figure 5. New Data Source

Data Source Name: Up to you

JNDI Name: this is up to you, but the standard naming convention should be;  jdbc/datasourcerefname.  For this example we will use jdbc/mysqlblogpost.

Select Next

Figure 6. Select an Exisiting JDBC Provider

Make sure on this screen you select the JDBC provider you setup earlier.

Select Next

Figure 7. Leave the default as is.

Hit Next and then Finish.  — Remember to save this to your master configuration.

Figure 8. Your Data Source List should look something like this now.

Select the data source you just created and select the JAAS-J2C authentication data link to the side.

Figure 9. JAAS List

Select New.

Figure 9. New User/Password Reference

Hit Ok, and Save.

Go back to your Datasource and select Custom Properties.

Either set or add the following properties.

After you add this..  Remember to save the changes to your master configuration.

Now lets get to your Application.

Setup a Resource Reference in your Deployment Descriptor.

When you deploy this application Websphere will ask you to map this resource.  You will be mapping it to the data source you just set up. jdbc/mysqlblogpost

<resource-ref>

<description>Your New DataSource</description>

<res-ref-name>jdbc/mysqlblogpostdataref</res-ref-name>

<res-type>javax.sql.DataSource</res-type>

<res-auth>Container</res-auth>

</resource-ref>

Then your Hibernate Configuration file can reference your web.xml’s reference.

That’s It!!  Happy Deploying!!

Thanks to Kevin Holman for this:

Netstat is the way to go to see which MS you are talking to “right now”.
netstat | findstr 5723
netstat -n | findstr 5723

The first one takes longer – but gives you the servername.
The second runs faster – but gives you the IP address.

The is the best way to determine who you SHOULD be talking to, your Primary. It will also show you a list of everyone the agent COULD fail over to, randomly.

Look in the config files (Goto \Health Service State\Connector Configuration Cache\ and open the xml file. Browse to and look for the management servers which is set to True.

Note
Looking in the registry will only show you who you were assigned to INITIALLY, at time of installation. It might not even be a real live management server anymore, or you might have moved the agent to talk to a different MS as primary.

• The Project temp, Steph, is leaving us Friday 27th November. Additional resources will be required.
• Drop down coded lists need to be developed. Recommendations will be made  at the Clinical Review group meeting next week.
• Service Questionnaires have been sent to the North Devon Clnical Team Leaders. This is a spreadsheet that needs to be populated with all staff names, team names, addresses etc to enable the configuration team to upload the data on to RiO so it will be correct in a working environment.
• The population of the Data Collection Workbook is on schedule for North Devon.

By default when you add a WCF Service reference in WPF, it does not give async functions. If your application needs async features, while adding a reference to the service, lookout for a ‘Advanced’ button on Add service reference window at bottom right corner. On clicking on that button, a new window appears. There is a checkbox called ‘Generate Asynchronous Operations’. Hit Ok and you are done!

Simple isn’t it

In the same location (as part 2), create another file called “applicationContext.xml”.  Paste in the following content.  Some explanation will follow below.

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:aop="http://www.springframework.org/schema/aop"
xmlns:tx="http://www.springframework.org/schema/tx"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx-2.5.xsd
http://www.springframework.org/schema/aop
http://www.springframework.org/schema/aop/spring-aop-2.5.xsd">

<bean
 class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
  <property name="location" value="classpath:database.properties"/>
</bean>

<bean
 id="dataSource"
 class="org.apache.commons.dbcp.BasicDataSource"
 destroy-method="close">
  <property name="driverClassName" value="${database.class}"/>
  <property name="url" value="${database.url}"/>
  <property name="username" value="${database.username}"/>
  <property name="password" value="${database.password}"/>
</bean>

<bean
 id="transactionManager"
 class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
  <property name="dataSource" ref="dataSource"/>
</bean>

<tx:annotation-driven/>

<bean
 id="sqlMapClient"
 class="org.springframework.orm.ibatis.SqlMapClientFactoryBean">
  <property name="configLocation" value="sqlmap-config.xml"/>
  <property name="dataSource" ref="dataSource"/>
  <property name="useTransactionAwareDataSource" value="true"/>
</bean>

<bean id="myDAO" class="com.example.dao.MyDAOImpl">
 <property name="sqlMapClient" ref="sqlMapClient"/>
</bean>

</beans>

Notes:

• classpath:database.properties points to the database.properties files we created earlier.  If you used a different location, you may need to update this value.
• sqlmap-config.xml is a file we will create later.  It will hold our sql and mapping information.
• myDAO is our data access interface.  This will be created later also.  You may need to change the name of this, and it’s class reference.

For example, you need to upload log file in case of error from desktop application to remote site using WCF service and if the log file is too big, you might have to tweak your WCF service’s Web.config.

By default the configuration for the service will be

      <services>
            <service behaviorConfiguration="ServiceBehavior" name="Service">
                <endpoint address="" binding="basicHttpBinding" contract="IService">
                </endpoint>
                <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
            </service>
        </services>

You need to specify the binding manually and add binding reference as highlighted below.   

    <services>
            <service behaviorConfiguration="ServiceBehavior" name="Service">
                <endpoint address="" binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IService" contract="IService">
                </endpoint>
                <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
            </service>
        </services>
        <bindings>
                <basicHttpBinding>
                    <binding name="BasicHttpBinding_IService" closeTimeout="00:01:00"
                        openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
                        allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
                        maxBufferSize="2147483647" maxBufferPoolSize="2147483647"
                        maxReceivedMessageSize="2147483647" messageEncoding="Text"
                        textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true">
                        <readerQuotas maxDepth="32" maxStringContentLength="2147483647"
                            maxArrayLength="2147483647" maxBytesPerRead="4096" maxNameTableCharCount="16384" />
                        <security mode="None">
                            <transport clientCredentialType="None" proxyCredentialType="None"
                                realm="" />
                            <message clientCredentialType="UserName" algorithmSuite="Default" />
                        </security>
                    </binding>
                </basicHttpBinding>
            </bindings>

That’s it Simple isn’t it?

" Ali Rizvi's Vim Settings

set number
set shiftwidth=4

set incsearch
set hlsearch
set textwidth=80

" from lindes:
syntax on
hi Comment term=bold ctermfg=Cyan guifg=Cyan
set autoindent

" from benji fisher to turn on the matchit plugin automatically and more
filetype plugin on

" explicity map file extension .t to perl syntax instead of tads
" which is autodetected by filetype plugin on
" This line should always be after filetype plugin
autocmd BufNewFile,BufRead *.t set syntax=perl

" to show real tabs and spaces in file
set list
set listchars=tab:>-,trail:^,eol:$
"set listchars=tab:>-,trail:-

"to add spaces instead of tabs
set expandtab

" evil, bad! -- hard tabs should be 8 chars... --lindes
" set tabstop=4
" _but_ we can use this:
set smarttab

"use arrow keys to move to previous and next buffers
nnoremap  :bn
nnoremap  :bp

"make the background light
set background=light

"show matching parens
set showmatch

"show row and column number
set ruler

" allow backspacing over everything in insert mode
set backspace=indent,eol,start

filetype plugin indent on

"set shiftwidth to 2 for ruby only
autocmd FileType ruby setlocal  sw=2

"shortcuts inspired by http://weblog.jamisbuck.org/2008/11/17/vim-follow-up
let mapleader = " "
map n :execute 'NERDTreeToggle ' . getcwd()

let g:fuzzy_ignore = "*.log"
let g:fuzzy_matching_limit = 70
map ft :FuzzyFinderTextMate
map fb :FuzzyFinderBuffer
map ff :FuzzyFinderFile =fnamemodify('**/x', ':p')
map fm :FuzzyFinderMruFile

command Ped :exec '!p4 edit %'
command Pad :exec '!p4 add %'

set backupdir=~/.vim-tmp
set directory=~/.vim-tmp

#
# Example of a user's .screenrc file
#

# This is how one can set a reattach password:
# password ODSJQf.4IJN7E    # "1234"

# no annoying audible bell, please
vbell on

# detach on hangup
autodetach on

# don't display the copyright page
startup_message off

# emulate .logout message
pow_detach_msg "Screen session of \$LOGNAME \$:cr:\$:nl:ended."

# advertise hardstatus support to $TERMCAP
# termcapinfo  * '' 'hs:ts=\E_:fs=\E\\:ds=\E_\E\\'

# make the shell in every window a login shell
#shell -$SHELL

# autoaka testing
# shellaka '> |tcsh'
# shellaka '$ |sh'

# set every new windows hardstatus line to somenthing descriptive
# defhstatus "screen: ^En (^Et)"

defscrollback 10000

# don't kill window after the process died
# zombie "^["
################
#
# xterm tweaks
#

#xterm understands both im/ic and doesn't have a status line.
#Note: Do not specify im and ic in the real termcap/info file as
#some programs (e.g. vi) will not work anymore.
termcap  xterm hs@:cs=\E[%i%d;%dr:im=\E[4h:ei=\E[4l
terminfo xterm hs@:cs=\E[%i%p1%d;%p2%dr:im=\E[4h:ei=\E[4l

#80/132 column switching must be enabled for ^AW to work
#change init sequence to not switch width
termcapinfo  xterm Z0=\E[?3h:Z1=\E[?3l:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;4;6l

# Make the output buffer large for (fast) xterms.
termcapinfo xterm* OL=10000

# tell screen that xterm can switch to dark background and has function
# keys.
termcapinfo xterm 'VR=\E[?5h:VN=\E[?5l'
termcapinfo xterm 'k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~'
termcapinfo xterm 'kh=\E[1~:kI=\E[2~:kD=\E[3~:kH=\E[4~:kP=\E[H:kN=\E[6~'

# special xterm hardstatus: use the window title.
termcapinfo xterm 'hs:ts=\E]2;:fs=07:ds=\E]2;screen07'

#terminfo xterm 'vb=\E[?5h$\E[?5l'
termcapinfo xterm 'vi=\E[?25l:ve=\E[34h\E[?25h:vs=\E[34l'

# emulate part of the 'K' charset
termcapinfo   xterm 'XC=K%,%\E(B,[\304,\\\\\326,]\334,{\344,|\366,}\374,~\337'
# xterm-52 tweaks:
# - uses background color for delete operations
termcapinfo xterm be

################
#
# wyse terminals
#

#wyse-75-42 must have flow control (xo = "terminal uses xon/xoff")
#essential to have it here, as this is a slow terminal.
termcapinfo wy75-42 xo:hs@

# New termcap sequences for cursor application mode.
termcapinfo wy* CS=\E[?1h:CE=\E[?1l:vi=\E[?25l:ve=\E[?25h:VR=\E[?5h:VN=\E[?5l:cb=\E[1K:CD=\E[1J

################
#
# other terminals
#

#make hp700 termcap/info better
termcapinfo  hp700 'Z0=\E[?3h:Z1=\E[?3l:hs:ts=\E[62"p\E[0$~\E[2$~\E[1$}:fs=\E[0}\E[61"p:ds=\E[62"p\E[1$~\E[61"p:ic@'

# Extend the vt100 desciption by some sequences.
termcap  vt100* ms:AL=\E[%dL:DL=\E[%dM:UP=\E[%dA:DO=\E[%dB:LE=\E[%dD:RI=\E[%dC
terminfo vt100* ms:AL=\E[%p1%dL:DL=\E[%p1%dM:UP=\E[%p1%dA:DO=\E[%p1%dB:LE=\E[%p1%dD:RI=\E[%p1%dC

################
#
# keybindings
#

#remove some stupid / dangerous key bindings
bind k
bind ^k
bind .
bind ^\
bind \\
bind ^h
bind h
#make them better
bind 'K' kill
bind 'I' login on
bind 'O' login off
bind '}' history

# Yet another hack:
# Prepend/append register [/] to the paste if ^a^] is pressed.
# This lets me have autoindent mode in vi.
register [ "33:se noai15a"
register ] "33:se ai15a"
bind ^] paste [.]

################
#
# default windows
#

# screen -t local 0
# screen -t mail 1 elm
# screen -t 40 2 rlogin faui40
# caption always "%3n %t%? @%u%?%? [%h]%?"
# hardstatus alwaysignore
# hardstatus alwayslastline "%w"

# bind = resize =
# bind + resize +1
# bind - resize -1
# bind _ resize max
#
# attrcolor u "-u b"
# attrcolor b "R"

# fix delayed vi/vim startup in screen
altscreen on

# something that would reload the .screenrc file on reattach
bind R source $HOME/.screenrc

# http://www.ibm.com/developerworks/aix/library/au-gnu_screen/index.html
hardstatus on
hardstatus alwayslastline
hardstatus string "%{.bW}%-w%{.rW}%n %t%{-}%+w %=%{..G} %H %{..Y} %m/%d %C%a "

Below is the latest, newest and shiniest addition to the family. Doesnt take a strain of the eyes to figure out what it is. Great – now we have horns and wind with the wood

Free a lancé les jeux sur la FreeBox HD. Il y avait déjà des possibilités de jeux à travers les télésites, mais cette fois un environnement dédié à cette activité est disponible, avec les facilités que cela sous-entend.

Dans ce billet, je vais vous présenter mon parcours du combattant pour l’installation d’Elixir et d’EFL sous Ubuntu 9.04.

Le SDK : JavaScript, Elixir et EFL

Avant d’aller plus loin, il est important de bien comprendre l’environnement dans lequel on arrive.

Tout d’abord, le langage de développement retenu par Free est le JavaScript. Et comme le JavaScript est un langage interprété, il faut un interpréteur ! Et c’est SpiderMonkey qui s’y colle, l’interpréteur JavaScript de Firefox.

Le JavaScript seul ne peut pas faire grand chose, à l’instar de n’importe quel autre langage. Dans un navigateur il a habituellement accès au DOM, ce qui lui permet d’interagir avec le contenu des pages web.

Dans la FreeBox, le code JavaScript que vous pourrez écrire ne s’exécute pas dans un navigateur. Pour pouvoir interagir avec l’affichage et la télécommande, les EFL viennent à la rescousse.

EFL ? En plus long, les Enlightenment Foundation Libraries. Il s’agit d’un ensemble de bibliothèques conçues à l’origine pour le gestionnaire de fenêtres Enlightenment. Dans la FreeBox, exit Enlightement, ne restent que les EFL.

Ces bibliothèques ne connaissant pas nativement SpiderMonkey, et réciproquement, il fallait une couche supplémentaire pour les faire communiquer : Elixir.

Le schéma suivant résument l’ensemble :

De façon non exhaustive, les EFL comptent :

• eet : une bibliothèque qui permet, entre autres, la création et la gestion de fichiers ressource (avec les fichiers .edj),
• evas : un gestionnaire de canevas (un équivalent Cairo),
• edje : un gestionnaire d’interface (un équivalent Glade).

Comment développer des jeux pour la FreeBox ?

Tout ce qui a été présenté à la section précédente est déjà installé sur votre FreeBox HD si vous avez un Firmware 1.6.1 ou supérieur.

Le développement de jeux et d’applications nécessitant des outils différents de la plateforme cible, il vous faut maintenant un environnement de développement sur votre machine.

Je suis sous Ubuntu 9.04 64 bits (pas encore fait le saut pour la 9.10).

Il me faut donc installer :

• SpiderMonkey,
• EFL,
• Elixir,
• edje_viewer.

Et c’est là que ça commence à devenir marrant

Ma procédure d’installation diffère quelque peu de la procédure officielle.

Installation de tout le schmurtz

Pré-requis

Installer gperf, libnspr4-dev, automake, svn et wget :

sudo apt-get install gperf automake svn wget libnspr4-dev

Notes :

• Les utilitaires svn et wget sont uniquement utilisés pour récupérer les fichiers nécessaires à l’installation du SDK. Ils pourront être désinstallés après l’installation d’Elixir.
• Libnspr4-dev est nécessaire pour la compilation de SpiderMonkey.
• Automake permet le lancement des scripts autogen.sh, nécessaires dans le cas de sources récupérés par svn (suite au commentaire de Strofe).

Récupération des sources

Créez-vous un répertoire elixir dans lequel vous exécuterez tout ce qui suit.

Récupérez les sources avec les lignes de commande suivantes :

mkdir elixir
cd elixir
wget http://elixir.freebox.fr/elixir/elixir-0.1.24.tar.bz2
tar xjvf elixir-0.1.24.tar.bz2
wget http://ftp.mozilla.org/pub/mozilla.org/js/js-1.8.0-rc1.tar.gz
tar xzvf js-1.8.0-rc1.tar.gz
svn co http://svn.enlightenment.org/svn/e/trunk/eina eina-svn
svn co http://svn.enlightenment.org/svn/e/trunk/eet eet-svn
svn co http://svn.enlightenment.org/svn/e/trunk/evas evas-svn
svn co http://svn.enlightenment.org/svn/e/trunk/ecore ecore-svn
svn co http://svn.enlightenment.org/svn/e/trunk/efreet efreet-svn
svn co http://svn.enlightenment.org/svn/e/trunk/embryo embryo-svn
svn co http://svn.enlightenment.org/svn/e/trunk/edje edje-svn
svn co http://svn.enlightenment.org/svn/e/trunk/e_dbus e_dbus-svn
wget http://download.enlightenment.org/snapshots/2009-07-29/elementary-0.5.1.0.tar.bz2
tar xjvf elementary-0.5.1.0.tar.bz2
svn co http://svn.enlightenment.org/svn/e/trunk/edje_viewer/ edje_viewer
wget http://freebox-elixir.googlecode.com/svn/trunk/exemples/ecore_evas/Simple.js

Notes :

• Suite à la judicieuse remarque de Superna en commentaire, vous pouvez remplacer les “svn co” par des “svn export” pour gagner en espace disque et en vitesse de téléchargement.
• Au moment où j’écris ces lignes, il existe apparemment une version 0.1.25 d’Elixir mais ce n’est pas celle qui est indiquée sur le site http://elixir.freebox.fr/
• On compile SpiderMonkey plutôt que d’installer les paquetages libmozjs-dev et libmozjs0d disponibles sous Ubuntu 9.04 car ces derniers ne définissent pas la constante JSVERSION_1_8 nécessaire à Elixir (ils s’arrêtent à JSVERSION_1_7).
• Le fait de récupérer les sources des EFL par svn plutôt qu’en allant sur http://download.enlightenment.org/snapshots/LATEST/ comme recommandé sur http://elixir.freebox.fr/ permet d’avoir une version à jour de evas. En suivant la procédure officielle, j’obtenais les messages suivants lors de la compilation d’Elixir :
  

  evas-const-binding.c:113: erreur: ‘EVAS_HINT_EXPAND’ undeclared here (not in a function)
  evas-const-binding.c:114: erreur: ‘EVAS_HINT_FILL’ undeclared here (not in a function)

• Les deux dernières lignes permettent de télécharger elementary et edje_viewer afin de compiler ce dernier. Il n’est pas indispensable mais est bien pratique pour voir graphiquement ce que contient un fichier .edj.
• Simple.js est un script qui permettra de vérifier le bon déroulement de la compilation et de l’installation d’Elixir.
• À la fin de l’exécution de ces lignes, tous les fichiers nécessaires ont été récupérés et décompressés dans le répertoire elixir.

Compilation et installation des EFL

Pour compiler les EFL, c’est un peu rébarbatif, il faut aller dans chacun des répertoires suivants :

• eina-svn,
• eet-svn,
• evas-svn,
• ecore-svn,
• efreet-svn,
• embryo-svn,
• edje-svn,
• e_dbus-svn.

Dans chacun de ces répertoire, il faut répéter les commandes suivantes :

sh autogen.sh
make -j4
sudo make install

Notes :

• On utilise “sh autogen.sh” plutôt que “sh configure” car il s’agit de versions svn qui ont besoin de générer le fichier configure. Autogen.sh fait les deux : création et exécution du fichier configure.
• L’option -j4 permet d’utiliser quatre cœurs pour accélérer la compilation. Si vous avez un processeur dual core, utilisez -j2.

Une fois les EFL compilées et installées, exécutez la commande suivante :

sudo ldconfig

Compilation et installation de SpiderMonkey

De retour dans le répertoire elixir, placez-vous maintenant dans le répertoire js/src.

make JS_THREADSAFE=1 JS_DIST=/usr -f Makefile.ref
sudo su
mkdir /usr/include/smjs
cp *.h /usr/include/smjs
cp *.tbl /usr/include/smjs
cp Linux_All_DBG.OBJ/libjs.so /usr/lib/libsmjs.so
cp Linux_All_DBG.OBJ/jsautocfg.h /usr/include/smjs/jsautocfg.h
exit

Note :

• Il s’agit de la procédure d’installation de SpiderMonkey telle que présentée dans la procédure officielle.

Une fois SpiderMonkey compilé et installé, exécutez la commande suivante :

sudo ldconfig

Compilation et installation d’Elixir

C’est au tour d’Elixir !

Avant de lancer la compilation, il va falloir modifier une ligne dans les sources d’Elixir. La version des EFL doit être un brin trop récente pour la version 0.1.24 d’Elixir. Si vous ne faîtes pas la modification, vous aurez droit aux lignes suivantes :

ecore_module.c: In function ‘elixir_ecore_thread_run’:
ecore_module.c:908: erreur: too few arguments to function ‘ecore_thread_run’

Placez-vous dans le sous-répertoire elixir-0.1.24 du répertoire elixir.

Éditez la ligne 908 du fichier src/modules/bindings/ecore/ecore_module.c. Elle ressembler à ceci :

result = ecore_thread_run(_elixir_func_heavy, _elixir_func_end, new);

Il faut la transformer en ceci :

result = ecore_thread_run(_elixir_func_heavy, _elixir_func_end, new,NULL);

Une fois la modification faite, compilez comme suit :

sh configure
make -j4
sudo make install

Une fois Elixir compilé  et installé, exécutez la commande suivante :

sudo ldconfig

Premier test

De retour dans le répertoire elixir, tapez la ligne suivante :

elixir Simple.js

Si tout s’est bien passé, vous devriez voir un rectangle se balader dans une fenêtre.

À partir de là, vous disposez d’un environnement complet pour créer vos jeux pour la FreeBox.

Compilation et installation de edje_viewer

On va tout d’abord installer la bibliothèque elementary. Placez-vous dans le sous-répertoire elementary-0.5.1.0 et lancez la compilation :

sh autogen.sh
make -j4
sudo make install

De retour dans le répertoire elixir, placez-vous dans le sous-répertoire edje_viewer et lancez la compilation :

sh autogen.sh
make -j4
sudo make install

Une fois elementary et edje_viewer compilés  et installés, exécutez la commande suivante :

sudo ldconfig

Et après tout ça ?

Récupérez les exemples, tutoriels et jeux

Pour vous faire la main, vous pouvez rapatrier les exemples, les tutoriels ainsi que les jeux livrés en standard. Pour cela, replacez-vous dans le répertoire elixir et tapez la ligne :

svn checkout http://freebox-elixir.googlecode.com/svn/trunk/ freebox-elixir

Résumé des commandes

Pour résumer, vous disposez désormais des commandes suivantes :

• elixir : permet d’exécuter votre code JavaScript (ex. : elixir Simple.js),
• edje_cc : pour compiler des fichiers .edc en fichiers .edj (edje_decc fait le contraire),
• eet : pour ajouter, supprimer des ressources des fichiers .edj (en partenariat avec elixir-compile),
• edje_viewer : pour voir graphiquement les ressources des fichiers .edj.

Tester ses programmes sur la FreeBox

Pour tester vos réalisations directement sur la FreeBox, il suffit de les placer dans le répertoire “Jeux” sur le disque dur de la FreeBox (par ftp sur hd1.freebox.fr, utilisateur freebox).

Si vous copiez Simple.js de cette façon, vous pourrez l’exécuter directement.

Pour les jeux livrés en standard, c’est plus sioux. Tous les fichiers ne sont pas nécessaires puisque le fichier .edj en intègre déjà une bonne partie.

Par exemple, pour le démineur, copiez les fichiers suivants dans un sous-répertoire demineur du répertoire Jeux sur le disque dur de la FreeBox :

• demineur_bomb.wav,
• Demineur.edj,
• Demineur.ogg,
• edje-helper.edj,
• freebox-mouse.png,
• high_score.wav,
• Scores.db.

Références

http://wiki.enlightenment.org/index.php/E17_User_Guide/Installing_from_Source_Repository

Installation d’Enlightenment 17 à partir des sources svn.

http://elixir.freebox.fr/?section=documentation

Procédure officielle d’installation d’Elixir

https://developer.mozilla.org/en/Building_only_SpiderMonkey

Procédure d’installation officielle de SpiderMonkey

http://code.google.com/p/freebox-elixir/wiki/InstallerElixir

Discussion à propos de l’installation d’Elixir sur Google Code

http://svn.enlightenment.org/svn/e/trunk/

Versions svn des bibliothèques nécessaires à la compilation d’Enlightenment

http://download.enlightenment.org/snapshots/LATEST/

Les dernières versions officielles des EFL.

204426     การปรับแต่งเครือข่าย     Network Configuration

แบบจํ าลองการเชื่อมต่อระหว่างระบบเปิด เครือข่ายบริเวณเฉพาะที่ การออกแบบและเอกสารสํ าหรับเครือข่ายบริเวณเฉพาะที่ ทีซีพี ไอพีและการกํ าหนดเลขที่อยู่แบบไอพี เครือข่ายบริเวณกว้าง ส่วนประกอบอุปกรณ์จัดเส้นทางและ การปรับแต่ง โพรโทคอลหาเส้นทาง การแก้ปัญหาในเครือข่าย เครือข่ายบริเวณเฉพาะที่แบบเสมือน การจัดการเครือข่าย การออกแบบเครือข่ายบริเวณกว้าง

(Open system interconnection model; local area network; local area network design and documentation; TCP IP and IP addressing; wide area network; router components and configuration; routing protocol; network troubleshooting; virtual local area network; network management; wide area network design.)

(204426 มหาวิทยาลัยเกษตรศาสตร์)

Recently I was asked how a CQ monitoring should be setup. The question was acompanied by a very short description, how the monitoring was supposed to look like. There were some points like “monitoring the publishing by requesting pages”, “check if the java process is running” and “checking the free disk space”. Obviously they just setup some new servers for this environment and thought that they need to monitor some parameters.

As a first step I advised to separate the topics “application monitoring” and “system monitoring”. One might wonder why I suggest to make a strong division between these topics, so here the background.

Standardization is one of the key topics in IT; everything, what is standardized, can be reused, can be exchanged by a compatible product, and finally lowers the cost. So IT operation teams tend to standardize as much as they can, because as intermediate step to lower costs standardization allows automation.

Basic system monitoring is such a thing. Every computer has componentes, which can be monitored such way: Disk health, CPU temperature, status of the power supply units, internal temperature. But also CPU utlization, free disk space, network connectivity or if the system starts to swap. And many more. These are basic metrics which can be measured and monitored in a consistent and automatic way.

For these points it doesn’t care if the system runs a data warehouse application, a mailserver or CQ. They are all the same and the reaction is really comparable if one of these monitored things fails: If a disk is dead, one needs to replace it (with not-so-old servers you can do this online and without service interruption). The procedure may differ from computer to computer, but the basic action is always the same: When the monitoring shows that a disk failed, lookup the type of the failed disk, get a new one, and go the computer and replace it according to the guidelines of the computer manufacturer. That’s it. You can handle some thousand servers that way with only a few people.

Running applications isn’t standardized that way. One application requires a Windows Server, other run because of their history only on big iron. One vendor offers performance guarantees only for linux systems, and other vendors don’t care about the platform as long as they have a Websphere Application Server as base. Some applications are designed to run centralized, other applications can be clustered. Some have good logging and messages you can use for diagnosis, others don’t have that and error causes must be detected with system tools like truss or strace.
So applications are highly non-standardized and often need special skill and knowledge in order to operate them. Automatisation is a very hard job here, and there must be support by management to get every part of the organisation in the right direction.

(As a side note: In my former life before I joined Day I worked in a large IT operation organisation where every application was somehow non-standard; some less, but also some completly out of every order. IT tried its best to create some kind of standardization, but the busineses often didn’t care that much about it; also developers didn’t knew much about IT operations, so “but it works on my machine!!” and “Just open the firewall, so these 2 components can talk to each other” was often heard in early project stages.)

These applications also need completly different kinds of monitoring. The implementation for SAP monitoring looks different than the application monitoring for a web application. The actions the take in case of problems probably differ even more; and when it comes to investigate on errors the webapplication administrator cannot do anything on the SAP system. And vice-versa.

So it’s advisable to separate the monitoring into 2 parts: The basic system monitoring and the application monitoring.

The system monitoring part can be done by one team for all servers. The application monitoring is too complex and too different, the actions sometime require so often special knowhow, that it must be adjustable to the needs of each application and application administrators.

As a final conclusion: Everytime a computer system is setup, put it into the basic system monitoring. So failing disks can get replaced.
And when the application administrator deploys the application on it, the special monitoring stuff is installed then.
Just because the needs and skills, which it takes to react on monitored issues, are very different.

BlazeDS offers a great mechanism to attach your flex application to backend services. In this brief overview we’ll configure flex to call a Java Class and return results. This overview assumes you’ve already setup your IDE with a basic Flex / BlazeDS project.

Main points we’ll cover

• Build the Java Class
• Expose the Class with Blaze on the server
• Configure Flex to find the Blaze service
• Build the Flex components to make the call

Build the Java Class

In your IDE switch to the Java view and create a new Java class. We’ll call it HelloFlex. Create a private variable called message. Set an initial value for this variable in the constructor. Finally create a getter method that returns the message string.

package com.grant;

public class HelloFlex {
private String message;
public HelloFlex(){
message=”HI Flex. this is Java. How are you?”;
}
public String getMessage(){
return message;
}
}

Expose the class with BlazeDS on the server

Under your web-inf directory you’ll fine a subdirectory called flex. Within there you’ll see the main config files blaze uses to set up the services. services-config.xml is the main file and has statements to include the others. For this example we’re creating a simple remoting service, so go ahead and open up the  remoting-config.xml. Here’s where we’ll set up the configuration for our reomting service.

Blaze calls exposed services destinations. In this remoting-config.xml we’ll set up a destination that points to our HelloFlex class.

Under the default-channels create a new destination as follows.

<?xml version=”1.0″ encoding=”UTF-8″?>
<service id=”remoting-service”
class=”flex.messaging.services.RemotingService”>

<adapters>
<adapter-definition id=”java-object” class=”flex.messaging.services.remoting.adapters.JavaAdapter” default=”true”/>
</adapters>

<default-channels>
<channel ref=”my-amf”/>
</default-channels>

<destination id=”helloflex”>
<properties>
<source>com.grant.HelloFlex</source>
</properties>
<adapter ref=”java-object” />
<channels>
<channel ref=”my-amf” />
</channels>
</destination>
</service>

Configure Flex to find the BlazeDS Service

Depending how you set up your workspace that set may already be done for you. In order for flex to know what channels and destinations are available, our application needs to know where these config files are. In Java, these files are in the class path and are included in the build process. In Flex we need to explicitly tell the compiler where these files are.

Right click on the project and choose properties. Under flex compiler you’ll see a textbox for additional compiler arguments. To configure the file location you’ll need an argument here called services which points to the location of your xml files.

You have two options now.

1) If the folder is part of your flex build path you can make a relative reference to the file using the –services=<file> format as follows. Notice the web-inf directory is not included in the definition. In this the folder containing the flex subfolder is on my build path.

2) If the folder is NOT on your build path you can point to the file location. This is the default method that FlashBuilder implements. We’ll use it for this example, however I suggest you move to a relative location style as soon as you can.

For an explicit file system location the flex option is slightly different. Here we use the –services “<file Location>” format. On my drive the option reads –services “C:\FlashBuilder\dev\MyProject\WebContent\WEB-INF\flex\services-config.xml”

Build the Flex components to make the call

Now we can get back to our flex components and make the actual call. First flip back over to your Flex Perspective and open your main mxml file.

First we’ll define the service:

<mx:RemoteObject id=”myService”  destination=”helloflex” />

The id is the name you’ll reference this service elswhere in your flex app. The destination of helloflex needs to match the destination name you entered in your remoting-config.xml

Next we’ll move to some visual components. First lets add a panel to hold our controls.

<s:Panel width=”100%” height=”100%”>
<s:layout>
<s:VerticalLayout/>
</s:layout>

</s:Panel>

And add a text box to display some results

<s:Panel width=”100%” height=”100%”>
<s:layout>
<s:VerticalLayout/>
</s:layout>

<mx:TextArea id=”result_text”/>

</s:Panel>

Now we’ll add a button on the page to use the service

<s:Panel width=”100%” height=”100%”>
<s:layout>
<s:VerticalLayout/>
</s:layout>

<mx:TextArea id=”result_text”/>
<mx:Button label=”Call Java” click=”myService.getOperation(‘getMessage’).send();”/>

</s:Panel>

This is a direct use of the RemoteObject myService. This is not a best practice. Typically you would have a function managing your calls and the button would utilize that function. For simplicity sake I’ve included the direct call for this demonstration. In this example you’ll notice we use the getOperation function and pass in the java method name we want to call.

If you were to run this now you would see no results. We have yet to define what happens when the service gets called. Lets do that now.

Create a script block to hold our action script and add a simple method that puts the response of our service in our textbox.

<fx:Script>
<![CDATA[
import mx.rpc.events.ResultEvent;
import mx.rpc.events.FaultEvent;
private function resultHandler(evt:ResultEvent):void
{
result_text.text = evt.message.body.toString();
}
]]>
</fx:Script>

To use this function we’ll go back to the service and add a handler to manage all responses.

<fx:Declarations>
<!– Place non-visual elements (e.g., services, value objects) here –>
<!– DEFINE REMOTE SERVICES WE’LL USE –>
<mx:RemoteObject
id=”myService”
destination=”helloflex”
result=”resultHandler(event)” />
</fx:Declarations>

Your completed code should look like this

<?xml version=”1.0″ encoding=”utf-8″?>
<s:Application xmlns:fx=”http://ns.adobe.com/mxml/2009″
xmlns:s=”library://ns.adobe.com/flex/spark”
xmlns:mx=”library://ns.adobe.com/flex/halo” minWidth=”1024″ minHeight=”768″>
<fx:Declarations>
<!– Place non-visual elements (e.g., services, value objects) here –>
<!– DEFINE REMOTE SERVICES WE’LL USE –>
<mx:RemoteObject
id=”myService”
destination=”helloflex”
result=”resultHandler(event)” />
</fx:Declarations>
<fx:Script>
<![CDATA[
import mx.rpc.events.ResultEvent;
import mx.rpc.events.FaultEvent;
private function resultHandler(evt:ResultEvent):void
{
result_text.text = evt.message.body.toString();
}
]]>
</fx:Script>
<s:Panel width=”100%” height=”100%”>
<s:layout>
<s:VerticalLayout/>
</s:layout>
<mx:TextArea id=”result_text”/>
<mx:Button label=”Call Java” click=”myService.getOperation(‘getMessage’).send();”/>
</s:Panel>

</s:Application>

That’s it! Run the application and pat yourself on the back. Congratulations! Your first end to end Flex-Java app.

Then you probably want to look at this post for geeks.  Software that helps you configure, secure and do other fun stuff.  Click here.

Here are some steps to perform after installing SQL Server:

http://www.sql-server-performance.com/articles/dba/post_installation_steps_p1.aspx

I usually keep a spreadsheet handy with all of “specialized” installation steps that I want to perform. My company uses a SharePoint wiki for configuration management, so after I perform the steps I enter them into the config mgmt wiki.

I wrote a while back about how I managed to add logging with log4net to my ProjectWhite tests in Visual Studio. However, after being forced to move my source code it suddenly didn’t work anymore eventhough I followed my amazing instructions. After trying a whole bunch of things out, one of them worked.

For log4net to work, the log4net.config file needs to be copied into the TestResult folder created by Visual Studios testrunner. In order to achieve this, enter the “Test” menu in VS, select “Edit Test Run Configurations”, “Deployment” and there, add your log4net.config file.

This made things work for me.

Note: I’m using the built-in testrunner in Visual Studio to drive my tests and not NUnit right now.
Note2: The first thing I did was setting it up as I did in my previous post, I haven’t tried to see if just adding the file to deployment is enough, it might not be.

Hats off to Dave Wickert (one half of the PowerPivot Twins!) – he’s been blogging like there’s no tomorrow and it’s getting harder and harder to keep up!  Saying this, he’s included on his blog, PowerPivotGeek.com, two great tips for PowerPivot:

1) Ensure when you install Excel 2010 that you also install Office Shared Tools, it contains VSTO which is necessary for the PowerPivot add-in to work properly.  You can read more in his posting: And oh, you need this one more thing.

2) When you save your workbooks, save them in cell A1 so that way when your workbook is saved to SharePoint, Excel Services will render the workbook properly centered.  For more info, check out his posting: Another tip – always save your workbooks at cell A1.

Enjoy!

Have you ever had to do something that you knew (you just KNEW) that lots of folks were going to scream – and scream loud – about? This is one of those cases – I can just feel it!

Ok, here goes. There have been several recent newsgroups postings concerning why we require domain accounts to install PowerPivot for SharePoint. Why must the farm account and the various service accounts be domain accounts. This causes lots of heartache for users that want to install demo or evaluation servers because we don’t support a standalone server. Well, we do support standalone, but it a different kind of standalone. Let’s get right into it.

First, let’s compare and contrast this requirement with SharePoint. SharePoint has two types of installations: standalone (which they do NOT support in production) and complete/farm. The standalone installation is for demo and evaluation purposes only. It has uses NETWORK SERVICE as the service account for many of its internal processes. It is right up front that it is NOT expandable into a production system; it has security issues acting across servers; etc. However, it gives you a nice “toy” to play with. Let’s be right up front about it – PowerPivot does not install nor does it support a SharePoint standalone server installation. And, oh while we are on the subject, SharePoint does not support local machine accounts within a farm configuration. In the SharePoint world, once you go to domains – you go all of the way with domains.

Read more…

While this is technically a pure SharePoint posting, we have found it useful in our labs. We have password resets all of the time and this cheat sheet was developed to make it as painless as possible. I hope you find it as useful as we do.

Step 1: Start Services.msc

• For each service using the machine account, update the password and start the service

Step 2: Start IIS Manager. Under Application Pools, select each of the app pools that use the account that you are changing:

• Click Advanced Settings
• Click Identity
• Set the username and password
• iisreset

Read more…

Okay, so after my success with the VirtualBox install of vTiger, I went to the office to try to install vTiger on the server again. This time I am following a couple walkthroughs that I found earlier here and here. The first link is how to do the initial install, and written very nicely on a forum. The second link is how to finish the installation using vTiger’s Installation Wizard (completely html/php based).

So, I completely removed the old database, deleted the entire directory of vTiger in /var, and re-extracted the files again (good thing I saved that .tar file). After getting apache2 setup, and working my way through, I got to the configuring of vTiger, and had access denied messages, seems I had forgotten I had altered the envvars for Apache on my last few attempts. At this point, everything seems to be flowing nicely. Now I take a moment and write down all the different users/passwords that are being used (mysql, vtiger, user accounts, etc)…

Well, that went off nicely, now we have an empty CRM that we can start using (as soon as I start adding users into it). I’ve also got a couple bandwidth monitoring things running (I think I’ll have to start using screen on this too). Got Dovecot, Postfix, and SSH configured.

TODO: Add users to the CRM, add the mail server to the CRM, get hostname configured properly (aside from localhost stuff), and finally contact the network provider to get NAT tables set up for this server.

WOW! Almost finished on this thing!