IBM Certification - WebSphere

3 Numbers after the test code and test title are (in sequence):

a. Test duration in minutes

b. Approximate number of questions

c. Passing score

1. IBM Certified Solution Developer - Web Services Development for WebSphere Application Server V6.1

1.1. Test 807 - Web Services Development for IBM WebSphere Application Server V6.1 (90 55 58)

2. IBM Certified Solution Developer - WebSphere Business Monitor V6.0.2 (Expiring)

3. IBM Certified System Administrator - WebSphere Application Server, Network Deployment V6.1

3.1. Test 253 - IBM WebSphere Application Server Network Deployment V6.1, Core Administration (90 54 53)

4. IBM Certified Advanced System Administrator - WebSphere Application Server Network Deployment V6.1

4.1. Test 806 - IBM WebSphere Application Server Network Deployment V6.1, Advanced Administration (120 52 55)

5. <IBM Certified System Administrator - WebSphere Commerce V6.0>

6. <IBM Certified Application Developer - WebSphere Commerce V6.0>

7. IBM Certified Solution Developer - WebSphere Integration Developer V6.1

7.1. Test 316 - IBM WebSphere Integration Developer V6.1 Application Development (120 57 57)

8. IBM Certified System Administrator - WebSphere Process Server, V6.1

8.1. Any 1 of the following tests:

a. Test 253 - IBM WebSphere Application Server Network Deployment V6.1, Core Administration (90 54 53)

b. Test 806 - IBM WebSphere Application Server Network Deployment V6.1, Advanced Administration (120 52 55)

8.2. Test 995 - IBM WebSphere Process Server V6.1, System Administration (90 53 62)

Note: The following test-taking sequence is recommended:

(253 or 806) --> 995

9. IBM Certified Business Process Analyst - WebSphere Business Modeler Advanced V6.1

9.1. Test 992 - IBM WebSphere Business Modeler Advanced V6.1, Business Analysis and Design (150 52 59)

10. IBM Certified Administrator for SOA Solutions - WebSphere Process Server V6.1

10.1. Any 1 of the following tests:

a. Test 253 - IBM WebSphere Application Server Network Deployment V6.1, Core Administration (90 54 53)

b. Test 806 - IBM WebSphere Application Server Network Deployment V6.1, Advanced Administration (120 52 55)

10.2.. Any 1 of the following tests:

a. Test 667 - Architectural Design of SOA Solutions (150 60 55)

b. Test 669 - SOA Fundamentals [2008] (90 54 67)

10.3. Test 995 - IBM WebSphere Process Server V6.1, System Administration (90 53 62)

Note: The following two test-taking sequences are recommended

(253 or 806) --> 995 --> (669 or 667)

(669 or 667) --> (253 or 806) --> 995

11. IBM Certified Solution Designer -- WebSphere MQ V6.0

11.1. Test 996 - IBM WebSphere MQ V6.0 Solution Design (75 49 59)

12. IBM Certified Solution Developer - WebSphere Message Broker V6.1

12.1. Test 315 - IBM WebSphere Message Broker V6.1, Solution Development (90 53 58)

13. IBM Certified Solution Developer - WebSphere DataPower SOA Appliances, Firmware V3.6.1

13.1. Test 289 - IBM WebSphere DataPower SOA Appliances, Firmware V3.6.1 (150 76 60)

14. <IBM Certified Application Developer - WebSphere Transformation Extender V8.2>

15. IBM Certified System Administrator -- WebSphere MQ V6.0

15.1. Test 994 - IBM WebSphere MQ V6 System Administration (75 52 59)

16. IBM Certified System Administrator - WebSphere Message Broker V6.1

16.1. Test 994 - IBM WebSphere MQ V6 System Administration (75 52 59)

16.2. Test 314 - IBM WebSphere Message Broker V6.1, System Administration (105 53 62)

Notes :

1. XX. <YYYY> --> low priority.

2. Especially for #8, #10 and #16, required more than 1 test.

Pengkodean Server IBM vs Server Sun

Sebelumnya gw sendiri juga rada pusing dengan stack server dari masing-masing principal diatas. Maklum, secara gw bukan orang hardware. Tapi dari beberapa informasi yang gw dapet dari sumber-sumber yang cukup terpercaya, gw coba tuliskan secara sederhana and ga ribet. Tapi kalo mau yang lebih kumplit, tanya sama yang jual yah. semoga berguna.

Tipe server IBM secara umum (dari paling murah sampe paling mahal):

xSeries: ini pake processor intel/amd. otomatis osnya itu kalo ga windows ya linux.

pSeries: ini pake processor powerpc. nama osnya AIX.

iSeries: ini processornya pake apa yah? nama osnya AS400 *ga yakin nih*

zSeries: ini sekelas mainframe, osnya zOS *ga yakin juga soalnya ga pernah nyentuh nih barang*

Tipe server Sun secara umum (dari paling murah sampe paling mahal):

xSeries: ini mirip dengan xSeriesnya IBM, pake processor intel/amd. osnya bisa windows atawa linux.

tSeries: ini sekelas pSeries, pake processor UltraSPARC T1/T2 dan T2+, osnya solaris.

mSeries: ini juga sekelas pSeries p550 keatas, osnya SPARC64.

Fyi, by default semua server sun ini osnya pake solaris.
Trus jangan lupa, masing-masing family itu masih punya beberapa tipe lagi.
Sebagai contoh:

xSeries Sun ada x4x40 (untuk amd) dan x4x50 (untuk intel).

tSeries Sun itu ada T5120, T5220, T5140, T5240, T5440.
Daaannn....untuk angka-angka itu punya arti masing-masing. Contoh: yang T5140 itu untuk yang ukuran 1 rack unit, T5220 itu untuk yang ukuran 2 rack unit.

ada yang mau nambahin? utk yg HP mengkale?

XSLT For Novice

What is XSLT?
XSLT stands for XSL Transformations
XSL stands for EXtensible Stylesheet Language, and is a style sheet language for XML documents.
XSLT is the most important part of XSL
XSLT transforms an XML document into another XML document
XSLT uses XPath to navigate in XML documents
XSLT is a W3C Recommendation
In this tutorial, we want to transform the following XML document ("Books.xml") into HTML document (“Books.html”) using XSLT document (“Books.xsl”)

Books.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
 <list>
  <book ID = "888">
   <author>John Smith</author>
   <title>New Cars</title>
   <price>$8.00</price>
  </book>
  <book ID = "999">
   <author>Dan Big</author>
   <title>Large Stories</title>
   <price>$9.00</price>
  </book>
 </list>

Books.xsl
 <?xml version="1.0" encoding="ISO-8859-1"?>
 <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <xsl:template match="/">
   <html>
    <head><title>Book List</title></head>
    <body>
     <table border="1" cols="3" width="100%">
      <xsl:apply-templates />
     </table>
    </body>
   </html>
  </xsl:template>
  <xsl:template match="book">
   <tr>
   <td><xsl:value-of select="@ID" /></td>
   <xsl:apply-templates select="title|price" />
   </tr>
  </xsl:template>
  <xsl:template match="title|price">
   <td><xsl:value-of select="." /></td>
  </xsl:template>
 </xsl:stylesheet>

Explanation
XSLT <xsl:stylesheet> Element
The <xsl:stylesheet> defines that this document is an XSLT style sheet document (along with the version number and XSLT namespace attributes).
XSLT <xsl:template> Element
The <xsl:template> element is used to build templates.
An XSL style sheet consists of one or more set of rules that are called templates.
A template contains rules to apply when a specified node is matched.
The match attribute is used to associate a template with an XML element. The match attribute can also be used to define a template for the entire XML document. The value of the match attribute is an XPath expression (i.e. match="/" defines the whole document).
XSLT <xsl:apply-templates> Element
The <xsl:apply-templates> element applies a template to the current element or to the current element's child nodes.
If we add a select attribute to the <xsl:apply-templates> element it will process only the child element that matches the value of the attribute. We can use the select attribute to specify the order in which the child nodes are processed.
XSLT <xsl:value-of> Element
The <xsl:value-of> element is used to extract the value of a selected node
The result is :
Books.html
<html>
 <head>
  <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
  <title>Book List</title>
 </head>
 <body>
  <table width="100%" cols="3" border="1">
   <tr>
    <td>888</td><td>New Cars</td><td>$8.00</td>
   </tr>
   <tr>
    <td>999</td><td>Large Stories</td><td>$9.00</td>
   </tr>
  </table>
 </body>
</html>

How to test using command line utility?
1. Download Xalan-Java.
2. Set the Java classpath to include xalan.jar, serializer.jar,xml-apis.jar, and xercesImpl.jar -- or another conformant XML Parser
3. Call java and the Process class with the appropriate flags and arguments (described below). The following command line, for example, includes the -IN, -XSL, and -OUT flags with their accompanying arguments -- the XML source document, the XSL stylesheet, and the output file:
  java org.apache.xalan.xslt.Process -IN Books.xml -XSL Books.xsl -OUT Books.html
  OR
  Create batch file
  Books.cmd
  java -classpath .;serializer-2.7.1.jar;xalan-2.7.1.jar;xercesImpl.jar;xml-apis.jar org.apache.xalan.xslt.Process -IN Books.xml -XSL Books.xsl -OUT Books.html
  pause

Resource
http://www.w3schools.com/xsl/
http://xml.apache.org/xalan-j/commandline.html

[SAP-MM] Tentang Batch

Ada 2 cara penanganan inventory material:
1. Normal: Plant – Material – Storage Location
2. Batch: Plant – Material – Storage Location – Batch Number

Struktur dari material master memungkinkan kita untuk me-manage stock by value (level plant dan company) dan by quantity (level plant, company, dan storage location).
Tapi terkadang tidak cukup hanya sampai level tersebut. Kadang kita perlu mengidentifikasi suatu material dari material lain yang hasil produksinya memiliki karakteristik yang berbeda (misalnya warnanya lebih gelap, atau ukurannya lebih kecil). Untuk keperluan tersebut, maka production lot atau batch number dapat digunakan.

Selain itu dengan batch handling, kita tidak hanya dapat in-house production lots, tapi juga production lots dari vendor.
Ada indikator batch management di material master record yang harus di-set pada saat pembuatan material. Nomor batch dapat diisi secara manual maupun otomatis melalui system.
Nomor ini harus unik pada level client, material level, dan plant level.
Standard R/3 untuk konfigurasi ini adalah nomor batch di-assign pada level plant.

Setiap batch mengandung 2 jenis data:
1. General data: tanggal kadaluwarsa, tanggal GR terakhir, dsb. Data ini di-define di master batch, dan berlaku untuk semua storage location.
2. Stock data: quantity data ini diatur pada masing-masing storage location.

Kedua data tersebut dibuat secara otomatis pada saat pembuatan GR pertama kali. Tetapi jika ada data tambahan yang ingin diberikan misalnya tanggal kadaluwarsa, maka data tersebut harus di-maintain secara manual.

Jangan lupa pada saat ingin melakukan goods movement, maka selain nomor material, nomor batch juga harus di-input untuk kasus ini.

Welcome

System.out.println("Hello, World!");