draining Arabic in Urdu!

gradually at the end of Zia era, i saw some Urdu words/phrase got Arabic conversion, even few are subject to FATWA-e-kufar, and mostly Pakistanis become highly speculate about their correct Arabic version use, some of them are now everyday practice, and original word/phrase has taken to act of kufar.

some for example:

1. khuda hafiz - allah hafiz

2. apna khayal rakhna - allah nigebaan

3. shukria - jazakallah

4. god - God

5. allah - Allah

6. bohat khoob, bohat ala = mashallah

7. every statement for future tense start with inshallah.

8. adaab/salam - initially to salam-o-alykum and lately Asalam-o-alykum in certain situation even Asalam-o-alykum wa rahmatullah.

9. naming person with one of the allah's 99 names - start with "abdul" and the person must always be called using "abdul" e.g. abdul samad, abdul shakoor etc...

10. shab-a-kher - allah hafiz

later this whole Urdu-Arabic back-and-fourth saga was clinch in three major factors:


1. introducing Arabic language as as subject in high schools curriculum, specially in Federal Board affiliated schools.

2. beard men initially lazy/philosophical look - lately became symbol of religious personality, even beard men were started calling mulvi saab, sufi saab etc...

3. shalwar kameez & kurta pajamaa suddenly became Islamic dress.

cheers

janamdin

turned 35, many whites among few left black, some black already left {hairs}, left more weaker then right {eyes}, oscillate 10% up & down {weight}, still good {bones}, no change {height}, reduced the intake {stomach}, got open, stable, mature, unsatisfied, eager, impatient but beautiful. {brain}.

cheers

oracle weblogic 11g certified system administrator

what? you didn't knew about it? and you thought i am lazy? lazy enough that i would never be able to write any IT certification exam after RHCE (7 years ago)? here is the proof! check and chill...

cheers! 

multiple ORACLE Documaker instances reading single jms/hornetq issue.

Documaker's snail waxed zero size PDF's on our production environment, and it took me a day to figure it out, whats wrong with it! :(

below is the setup we had in our production environment.

whats happening here is, that two Documaker instances are reading from single/same jms/hornetq queue, and as Documaker does not have any identifier mechanism for soap messages, as it seems both tries to hold the message and somehow destroys the soap message arrived from ETPM in jms queue, so both Documaker instances endup with generating ZERO size PDF's.

the workaround is to run single Documaker instance per jms/hornetq queue. But this way you d'nt have real time fail-over for Documaker, you have to do manual switching in case of failure!

cheers.

hornetQ high available cluster, step by step

well, unlike jboss cluster, hornetq cluster work on shared/common storage space that could be a SAN shared disc or even NFS mount, though best option is SAN disc, you must keep in mind that both cluster members will not write simultaneously on shared disc as oracle RAC do, but they will use it to validate master/live server health, soon master/live server die, slave/backup server will replace it and from passive started state will move to active started state and all persistent messages of queues will be served from slave/backup server. This failover process is automatic, even when master/live server will come back online, the slave/backup server will again set itself automatically to passive started mode and will leave master/slave to take the control of queues and client requests/responses.

hornetQ offer two type of cluster solution i.e. load-balance plus failover and just failover not load-balance, in our case we is used just failover not load-balance. i have little edited the official hornetq cluster diagram, below, because for no good reason they made shared storage in two separate places and then the storage show no link among each other, while actually it must be single storage with link to both Live and Backup server.

for more details you must consult official guide or check below my step by step for hornetQ cluster installation.

the startup script was made by our development team as they like to pass JVM arguments inside script, though yo can use default run.sh which is more easy to understand.

find below step by step for hornetQ high available cluster.

Download

Cheers

ETPM, Documaker, JMS, LDAP, Database, Conceptual and abstract workflow diagram

ladies, if you are unable to understand how ORACLE ETPM, ORACLE Documaker, JMS/HornetQ, LDAP/OpenDS and Database/Exadata should work together, here is the lazy drawn diagram, i hope you will get an idea about what i have been implementing recently :)

you may consider it as ETPM application data center conceptual design as well;

Cheers

step by step ORACLE Documaker 12.0 installation & configuration on Linux 64x

believe me or not, but this one is gem, it is almost impossible to understand installation steps from ORACLE's bleeding ass Documaker installation manuals, i took the courage to prepare it, you must contact me if you get confused at some step!

here we go:



step 01: download V29335-01 & V29336-01 from edelivery.oracle.com

step 02: download jre1.6_0_32 from oracle.com

step 03: copy all downloads to /u01/app/documaker/documaker-source

step 04: install JRE 32bit

[cissys@documaker-host documaker-source]$ cd /u01/app/documaker/documaker-source
[cissys@documaker-host documaker-source]$ chmod +x jre-6u32-linux-i586.bin
[cissys@documaker-host documaker-source]$ ./jre-6u32-linux-i586.bin
[cissys@documaker-host documaker-source]$ mv jre1.6.0_32/ ../

step 05: install Documaker engine

[cissys@documaker-host documaker]$ mkdir rel120p01
[cissys@documaker-host documaker]$ mkdir dm-env
[cissys@documaker-host documaker]$ cd documaker-source
[cissys@documaker-host V29335-01]$ chmod +x * -R
[cissys@documaker-host V29335-01]$ ./setuprterp120p01b15380.lnx

* * * Documaker RP 12.0 (Turnover Level p01b15380) (Type RTE) Installation/Update * * *
Loading, Please Wait ...




Please select an Installation/Update Directory:
Press to accept default:
?>/u01/app/documaker/rel120p01


Install Documaker RP 12.0 (RTE) to ?
{y or n}?>y


Updated Base Components ...


...
RTE Installation Complete.

[cissys@documaker-host documaker-source]$ cd V29336-01
[cissys@documaker-host V29336-01]$ chmod +x *
[cissys@documaker-host V29336-01]$ ./setuprteids023p00b713.lnx

* * * Docupresentment 2.3 (Patch Level p00b713) (Type RTE) Installation/Update * * *
Loading, Please Wait ...




Please select an Installation/Update Directory:
Press to accept default:
?>/u01/app/documaker/dm-env


Install Docupresentment 2.3 (RTE) to ?
{y or n}?>y


Install/Upgrade in progress.  Please wait...
Updated Base Components ...


Install/Upgrade Base Components Complete.


Where is your 32-bit Java Run-time (JRE) Location?
 ( Example:  /opt/jdk1.6.0_24_x86/jre )
?>/u01/app/documaker/jre1.6.0_32
JRE Version=java version "1.6.0_32"


Option for WatchDog Error SMTP Email Notifications:
Do you want to configure this option now?
  (Note: You can manually configure it later in the log4j logconf.xml file)
{y or n}?>n
Continuing...
Installing Setup Files ...
Please Wait ...
New Installation Components Installed ...


RTE Installation Complete.

[cissys@documaker-host V29336-01]$ ./sharedobjs120p01b15380.lnx

* * * Documaker RP Shared Objects Bridge 12.0 (Turnover Level p01b15380) Installation/Update * * *
Loading, Please Wait ...




Please identify your Docupresentment Installation/Update Directory:
Note: Docupresentment directory must already exist.
Press to accept default:
?>/u01/app/documaker/dm-env/docserv


Install Docupresentment Documaker RP Shared Objects Bridge 12.0 (Turnover Level p01b15380) to ?
{y or n}?>y


Installation/Update in progress.  Please wait...
Updated Base Components ...


Installing Setup Files ...
Setup files detected (docserv.ini|docserv.xml)
Overwrite setup files?{y or n}?>y
Overwrite in progress...
Please Wait ...
New Documaker RP Shared Objects Bridge Installation Components Installed ...


Running logconfconvert.sh
Results:


logconf.xml.new
Setting up docserv.xml to use jre located at ...


Installation Complete.
step 06: start/stop documaker

[cissys@documaker-host docserv]$ cd /u01/app/documaker/dm-env/docserv
[cissys@documaker-host docserv]$ ./docserver.sh status/start/stop

step 07: configuration of Documaker environment.

[cissys@documaker-host docserv]$ cd /u01/app/documaker/dm-env/docserv
[cissys@documaker-host docserv]$ cp ../../documaker-source/dm-env_orig/dm-env/docserv/docserv.xml 
[cissys@documaker-host docserv]$ cp ../../documaker-source/dm-env_orig/dm-env/docserv/logconf.xml 
[cissys@documaker-host docserv]$ cp ../../documaker-source/uat_orig/dm-env/docserv/dap.ini .
[cissys@documaker-host docserv]$ cp ../../documaker-source/uat_orig/dm-env/docserv/app.ini .
[cissys@documaker-host uat]$ vi /u01/app/documaker/dm-env/mstrres/appdir/app.ini


cheers