Dynamic AX Installation Tutorial


microsoft-dynamics-ax

hi semua, akhirnya ada kesempatan nulis lagi nihh, berhubung tema tulisan sebelumnya adalah persiapan yang dibutuhkan untuk melakukan installasi dynamic AX 2009, nahh skrg kita akan bahas tutorial untuk installasinya ya. untuk penggunaan tiap modulenya nanti akan dibahas di kesempatan berikutnya.

berikut material yang dibutuhkan untuk melakukan installasi Microsoft Dynamic AX :

  1. RDBMS
    kita butuh database untuk store data2 AXnya, untuk databasenya sendiri direkomendasikan untuk menggunakan database enterprise level ex : SQL Server, Oracle, dsb, untuk installasi databasenya nanti juga akan dibahas dilain waktu dan kesempatan.
  2. software Microsoft Dynamic Axnya,
    untuk softwarenya sendiri saat ini kita menggunakan Dynamic AX 2009 jadul memang tp masih okelah untuk handle kebutuhan tempat saya bekerja 🙂

 

kalau kedua komponen diatas sudah ready artinya kita sudah bisa mulai melakukan installasi untuk microsoft Dynamic AXnya.

untuk step awal ya seperti biasa eksekusi dulu exe filenya dari microsoft dynamic AX 2009 seperti dibawah ini :

  1. step pertama adalah eksekusi exe file dari dynamic ax sendiri kemudian click tombol next.

ax1

ax2

ax3

sampai disini ada 2 role yang bisa dipilih,

pertama adalah custom installasi yang mana opsi ini adalah opsi customisasi per modulnya, di opsi ini kita dibolehkan hanya memilih modul2 yang akan kita gunakan saja.

kedua adalah developer installasi untuk opsi ini semua modul AX akan dibuka termasuk modul untuk melakukan developmentnya.

setelah sudah memilih maka klik tombol next

kemudian kita diharuskan untuk melakukan pemilihan koneksi ke database, sangat dianjurkan untuk melakukan penginstallan database terlebih dahulu sebelum melakukan installasi ms dynamic ax ini.

ax4

setelah melakukan pemilihan database, kita lanjut ke step berikutnya yaitu menentukan path untuk lokasi installasinya seperti berikut :

ax5

setelah itu masukan informasi komputer tempat dimana kita melakukan installasi database untuk dynamic AX tersebut.

ax6

ax7

ax8ax9

untuk step berikutnya adalah pemilihan account yang mana AOS service ini akan di running menggunakan account tersebut.

ax10

masukan bahasa yang ingin digunakan

ax11

ax12

setelah itu akan ada informasi bahwa semua component sudah siap untuk melakukan installasi ke tahap berikutnya, pilih “Install”

ax13

tunggu proses installasinya sampai selesai.

ax14

setelah proses installasi selesai akan ada informasi berikut

ax15

setelah installasi untuk dynamic ax servernya selesai, step berikutnya adalah installasi untuk client sidenya.

berikut stepnya :

eksekusi exe file dari dynamic ax 2009 client

ax16

ax17

klik next sampai selesai,

ax18

dan finish untuk installasi client dari dynamic axnya. begitu juga untuk artikel ini, penulis cukupkan dulu sampai disini, semoga nanti di kesempatan berikutnya penulis bisa membahas dari sisi useability per modulnya untuk microsoft dynamic ax ini (Account payable, Account Receivable, Inventory Management, Production, Master Planning, dll). so stay tune di blog sederhana penulis untuk materi berikutnya ya. ^_^

 

semoga bermanfaat.

 

Advertisements

Persiapan untuk Implementasi Microsoft Dynamic AX 2009


microsoft-dynamics-ax

nahh ini thread lanjutan dari thread perkenalan implementasi dynamic ax 2009 yg blm lama ini penulis posting,

dalam thread kali ini akan lebih membahas seputar system requirement dalam implementasi dynamic ax 2009,

adapun requirementnya sebagai berikut :

  • review system requirement
  • buat akun domain (selain administrator domain)
  • konfigurasi domain untuk kerberos auth
  • verify untuk permission untuk installasi
  • buat shared directory
  • pilih installation type

kita akan bahas satu persatu untuk requirementnya kecuali untuk review system requirement :

  • buat akun domain
    • microsoft dynamic ax implementasi membutuhkan beberapa services untuk running, maka dari itu dibutuhkan domain user yg setara dengan admin.
    • password never expired
    • mempunyai akses ke network resources
  • create domain accounts untuk SQL server services
    • SQL server database engine account
    • SQL server reporting services account
    • SQL server analysis services account
  • create domain accounts untuk microsoft dynamic AX services
    • AOS service account
    • Business Connector proxy account
    • Workflow service account
    • Workflow execution account
    • Synchronization service account
  • create domain accounts untuk sharepoint services
    • Sharepoint configuration account
    • SSP application pool identity account
    • SSP service account

Konfigurasi domain untuk kerberos authentication, duh untuk yg satu ini penulis blm pengalaman pegangnya ni, tp singkat cerita aja, kerberos itu authentication Single Sign On (SSO) untuk windows server sih, itu aja ya. hehehe, untuk kerberos sih sepertinya baru akan terasa kalau di implement level domain controller ber layer. kalau cuma single DC sih ga perlu lah ya, ngeribetin aja..

Create Shared directory

sebetulnya sih ini ga terlalu penting untuk dibahas, intinya cuma buat share directory lalu content installernya diambil dari share dir itu, tp gpp penulis bahas juga deh karena ini tercakup di preinstallation dokumen dari dynamic ax

  • create dir dengan nama AXSetup
  • share AXSetup directory
    • kasih full kontroll priviledge untuk administrator atau owner
    • dan kasih everyone akses untuk read, tp lebih amannya read & write
  • buat subdirectory dengan nama DynamicsAX2009
  • copy semua konten ke directory tersebut

step berikutnya adalah Select Installation Type

dalam hal ini ada 2 tipe installasi custom & developer installasi.

untuk production environment pilih custom installation untuk memilih specifi MS dynamic ax component, termasuk apabila kalau infranya menggunakan clustering system dan ingin diinstall per modulenya di server terpisah.

untuk testing environment pilih opsi developer installation untuk menginstall basic microsoft Dynamic Ax system pada single komputer, termasuk komponen berikut :

  • database
  • Application Object Server (AOS)
  • Application files
  • Client
  • .NET Business Connector
  • Debugger

sekian dulu untuk persiapan installasi microsoft Dynamic AXnya.

Microsoft Dynamic AX Implementation (perkenalan)


Hallo Semua dah lumayan lama ni ga nulis, hehe

sehubungan dengan pindahnya penulis ke kantor baru, ga usah sebut merk lah ya, dapat challenge baru yg lumayan ngeri ni, implementasi salah satu produk ERP dari microsoft,

yups microsoft dynamic ax versi 2009 tepatnya, untuk implementasi kali ini sepertinya akan banyak partnya ni, kita start dari sejarah AXnya :

microsoft-dynamics-ax

Microsoft Dynamics AX awalnya dikembangkan sebagai Axapta di Damgaard denmark sebelum digabung dengan Navision Software A / S pada tahun 2000. Perusahaan gabungan, awalnya NavisionDamgaard, kemudian Navision A / S, kemudian akhirnya diakuisisi oleh Microsoft Corporation di musim panas 2002. Sebelum merger, Axapta awalnya dirilis pada Maret 1998 di Denmark dan pasar AS. Saat ini, tersedia dan didukung dalam empat puluh lima bahasa di sebagian besar dunia.

AX Custom pengembangan dan modifikasi dilakukan dengan IDE sendiri, MorphX, yang berisi berbagai alat seperti debugger, kode analyzer, dan antarmuka pencarian. Lingkungan pengembangan ini berada di klien yang sama aplikasi yang normal sehari-hari pengguna akan akses, sehingga memungkinkan pembangunan akan berlangsung pada setiap instance dari klien. Perkembangan bahasa yang digunakan dalam Axapta adalah X + +.

On May 26, 2008, Microsoft selesai mengembangkan versi terbaru (2009) dalam fasilitas yang merentang di dunia dan termasuk situs dalam Vedbæk, denmark; Kiev, Ukraina; Fargo, North Dakota, Amerika Serikat; dan Redmond, Washington, Amerika Serikat; Karachi, Pakistan.

Sejarah menjadi jelas dalam konsep dicampur dalam desain dan pemrograman dan dalam dokumentasi rudimenter yang telah dipindahkan ke sebagian besar (yang dianggap lebih baik daripada menyediakan dengan kontradiksi atau informasi yang salah).

sumber:http://en.wikipedia.org/wiki/Microsoft_Dynamics_AX

IBM Big Fix Deployment (architecture)


Basic deployment

This is a very simplified deployment that points out the basic hierarchy and the ports used to connect the components.

Big Fix Basic Deployment

Big Fix Basic Deployment

Note the following about the diagram:

  • Port 80 is used to collect Fixlet messages over the Internet from Fixlet providers such as IBM.
  • A dedicated port (defaulting to 52311) is used for HTTP communications between servers, relays, and Clients.
  • A dedicated port (defaulting to 52311) is used for HTTPS communications between servers and Consoles.
  • Relays are used to share the server load. This diagram only shows two relays, but you can use dozens or even hundreds of relays in a similar flat hierarchy. Typically a Relay is deployed for every 500-1,000 computers.
  • The BigFix relays can also take advantage of a UDP port to alert the Clients about updates, but this is not strictly necessary.
  • The BigFix Clients are typically PCs or Workstations, but can include other servers, dockable laptops, and more. Any device that can benefit from patches and updates is a candidate to include in the deployment.

BigFix has far greater flexibility and potential than this simple case suggests. It is capable of overseeing hundreds of thousands of computers, even if they are spread out around the world. The next scenarios build on this basic deployment.

Main Office with Fast-WAN Satellites

This configuration is common in many universities, government organizations, and smaller companies with only a few geographical locations. This type of deployment is relatively easy to set up and administer because there are no (or very few) slow WAN pipes to consider.

Note the following about the diagram:

  • In this configuration, the relays are used both to relieve the server and to distribute the communications, optimizing the bandwidth.
  • This scenario has large WAN pipes, so office relays can communicate directly with the main server. A thin WAN could force a change in the layout of the relays (see the scenarios above and below).
  • The more relays in the environment, the faster the downloads and response rates.
  • Because of the nature of this network, when the clients are set to Automatically Locate Best relay, many of the relays are the same distance away. In this scenario, the clients automatically load-balance themselves amongst all the relays that are nearby.
  • For this high-speed LAN, a relatively flat hierarchy is recommended, with all relays reporting directly to the main server. Any extra levels in the hierarchy would only introduce unnecessary latency. However, if there were over 50-100 relays in this environment, another level of relays should be considered.

 

Disaster Server Architecture

Companies with sensitive or high availability needs might want to deploy multiple, fully-redundant servers to maintain continuous operation even in the event of serious disruptions. Multiple servers also help to distribute the load and create a more efficient deployment. Here is a simple diagram of how multiple servers might be set up to provide redundancy:

In case of a failover, the specific configured relays automatically find the backup server and reconnect the network. For more information about the relay configuration see Configuring relay failover.

Note the following about the diagram:

  • The BigFix servers are connected by a fast WAN, allowing them to synchronize several times per hour.
  • The servers need both an ODBC and an HTTP link to operate and replicate properly.
  • There is a primary server with an ID of 0 (zero). It is the first server that you install, and it is the default server for running the BigFix Administration Tool.
  • For the sake of clarity, this is a minimal configuration. A more realistic deployment would have a top-level relay and other WAN connections to regional offices.
  • The BigFix servers and relays are configured so that control can be automatically routed around a server outage (planned or otherwise), and upon failover reconnection, the databases are automatically merged.
  • The BigFix servers communicate on a regular schedule to replicate their data. You can review the current status and adjust the replication interval through BigFix Administration > Replication. For the best possible performance, these pipes should be FAT.
  • This diagram only shows two servers, but the same basic architecture would apply to each additional server. With multiple servers, a shortest-path algorithm is used to guide the replication.
  • When an outage or other problem causes a network split, it is possible for a custom Fixlet or a retrieved property to be modified independently on both sides of the split. When the network is reconnected on failover, precedence goes to the version on the server with the lowest server ID.

Efficient relay setup

To increase efficiency and reduce latency, this company has set up a hierarchy of relays to help relieve the server load. Each relay they add takes an extra burden off the server for both patch downloads and data uploads. Setting up relays is easy, and the clients can be set to automatically find the closest relay, further simplifying administration.

Note the following about the diagram:

  • There is a dedicated server computer known as the Top-Level relay that is used to take the load off the server computer.
  • All relays are manually configured to point to either the top level relay or to another relay that is closer. The general rule for configuring relays is that you want as few levels as possible to the relays unless there is a bandwidth bottleneck. Communications over thin pipes should be relay to relay. The top-level relay relieves the server, and the secondary relay allows a single download to be distributed over hundreds of clients.
  • There is a relay in the DMZ set up with a special trust relationship with the server. This relay allows clients in the DMZ or on the public Internet to be managed by BigFix. The DMZ places a security firewall between the relay and the set of home computers and laptops reporting in from the Internet.
  • This diagram shows a single relay in the large regional office. However, for offices with more than a few hundred clients, there will typically be multiple relays to effectively distribute the load.
  • As a general rule, you should deploy at least one relay per 500-1000 clients to maximize the efficiency of the relay. For more information see the article on relays at the BigFix support site.

Hub and spoke

This scenario involves a main data center, a small number of large regional offices, and many small regional offices. This configuration is common in large international organizations. The IBM BigFix clients are installed on computers in offices all around the world. Many of these locations have slow WAN connections (8 kbps-512 kbps), but there are many offices with faster WAN connections (1mbps-45mbps).

Often these locations are configured in a hub-and-spoke arrangement. This scenario builds on the previous one, but the hub-and-spoke configuration permits more levels in the relay hierarchy.

Note the following about the diagram:

  • In this scenario, the relays are carefully deployed at the proper junctions within the WAN to optimize bandwidth. Poor placement of relays can adversely impact your network performance.
  • It is vital that at least one relay is installed in every location with a slow WAN connection. Often a company already has a server in just such a location, acting as a file server, print server, AV distribution server, SMS distribution server or domain controller, or any other computer. The BigFix relay is usually installed on these existing computers.
  • To provide redundancy in a typical office, more than one relay should be installed. If a relay fails for any reason (powered down, disconnected from the network, and so on.), its attached clients can then automatically switch over to a different relay. A redundant relay is less important in very small offices because fewer computers are affected by the failure of a relay.
  • When the clients are set to Automatically Locate Best Relay, they will choose the closest one. If any relay fails, the clients automatically seek out another relay. You should monitor the relay configuration after the initial automated setup (and periodically after that) to ensure that the clients are pointing to appropriate locations. Talk to your support technician for more details about how to protect against overloading WAN pipes with BigFix data.
  • Bandwidth throttling at the relay level is very helpful in this configuration. The BigFix relays are set up to download slowly across the WAN pipes so as not to saturate the slow links. For more information see the article on throttling at the BigFix support site.
  • Instead of pointing to the main server, the relays are configured to point to the top level relay. This frees up the server to couple more tightly to the console and improves reporting efficiency.

The BigFix relays are configured to manually create the optimal hierarchy. The hierarchy has three levels (from the top down):

  1. The top-level relay that connects directly to the server.
  2. The regional office relays that connect to the top-level relay.
  3. Multiple branch office relays that connect to specified regional office relays.

Remote Citrix / Terminal Services Configuration

Although BigFix can efficiently deliver content even over slow connections, the console itself is data-intensive and can overwhelm a link slower than 256 kbps. Adding more Clients further increases the lag time.

However, you can access the console remotely from a Citrix, Windows Terminal Server, VNC or Dameware-style presentation server and realize excellent performance. Here is what this configuration looks like:

Note the following about the diagram:

  • In the main office, the console is set up on a computer that is close to the server for fast data collection. This is your Presentation server.
  • You must create user accounts for each remote user. These users can then access the console quickly because the time-critical data loading is done at the main office over a fast link.
  • Your remote connection can be over HTTPS to improve security.
  • Note that running a console from a Presentation server containing the private key is inherently less secure than if the key is stored on a removable drive.
  • You might be able to benefit from load-balancing software to spread the remote accesses across multiple servers.
  • The main bottleneck for a console running on Citrix is memory size. If the console runs out of memory, its performance decreases sharply. A good technique to determine the memory requirement is to open the console as a Master Operator. Check the memory used: this indicates the maximum memory requirement per user. Then log in as a typical operator and use this as your average memory requirement. If your Citrix server can support all concurrent users with the maximum memory then a single box suffices. If not, then use the average memory requirement per user to determine how many extra Citrix servers you might need.
  • The second constraint is CPU power. During refreshes, the console works best with a full CPU core. This means the Presentation server will be optimized with one CPU core running the console for each concurrent user.
  • The final concern is disk space for the console cache. You can understand the size of the cache by looking at an example on your local computer: C:\Documents and Settings\<USERNAME>\Local Settings\Application Data\BigFix\Enterprise Console\BES_bfenterprise. There should be enough disk space to provide one cache file for each console operator.

 

PROTECT YOUR ORGANIZATION FROM RANSOMWARE


Crypto-ransomware is one of the most dangerous types of malware ever created. The consequences of it can be very severe. We believe there are ways to protect your organization against this type of threat. 

 

  1. Back-up is a must.Upon the infection of your corporate PCs, the ransomware is likely to start encrypting files that are required for the daily work of your company. If it is technically impossible to back-up all the files you have in the corporate network, choose the most critical (accounting documents, clients’ data, legal documents etc.), isolate them and back-up regularly.

 

  2. Use a reliable, corporate-grade security solution and don’t switch off its advanced features, as these enable it to catch unknown threats.

 

  3. Undertake regular patch management.

 

  4. Educate your personnel,very often the ransomware infection happens due to a lack of knowledge about common cyberthreats and the methods criminals use to infect their victims.

 

  5. Avoid paying a ransom and report the attack to police.

 Source from kaspersky endpoint security

QlikView Displaying Data Population Pyramid


Hello sobat bloggers, dh lama tak bersua ni, update blog dikit ahh, hehe.. kali ini saya mw bahas dikit mengenai Qlikview application ni, tools yang cukup powerfull untuk create report. sebenernya sih saya juga masih belajar mengenai tools ini, tp gpplah sharing2 kali aja ada yang mw nambahin atau ngasih masukan mengenai BI Tools satu ini..

pokok bahasannya seputar displaying data populasi pyramid.

sebelum masuk ke materi sobat blogger bisa unduh material trainingnya dulu di link berikut :

Material Document

dan pastikan di unzip di folder yang sama, instruksi dari websitenya sih gitu 😛

lalu lalu lalu, buka qlikview applikasinya dong pastinya, dan klik qvw dokumennya dari materi training tadi.

pasti hasilnya nihil deh alias zonk, hal ini karena pada saat qlikview execute scriptnya data source excel path locationnya tidak ketemu,

berikut scriptnya :

[US Population]:
LOAD Year,
State,
Sex,
[Age range],
Population
FROM
[D:\System Development\QLIKVIEW\Tutorial\Displaying Data\DisplayingData-PopulationPyramid//*path dari data roucenya dalam hal ini excel dokumen\//*nama file yang akan di grep datanya di qlikviewUSPopulation.xlsx]
(ooxml, embedded labels, table is [US Population 1975-2011]);

setelah itu kita cek data modelnya dengan menggunakan CTRL + T, kemudian klik kanan di tablenya dan pilih preview.

display visualisasi populasi dalam bentuk piramida

berikut step by stepnya :

  1. klik kanan di kanvas qlikview dan pilih new sheet object –> chart lalu next
  2. pilih chart tipe lalu next
  3. masukan dimensi yang diinginkan dalam hal ini age range lalu next
  4. pada tab expression tambahkan expression untuk male and female dengan script berikut :
    • untuk male    : -Sum({$<sex={‘female’}>}Population)
    • untuk female : Sum({$<sex={‘female’}>}Population)
    • kemudian pilih next
  5. pada tab berikutnya untuk load ordernya dibuat reverse lalu next
  6. pada tab berikutnya subtype pilih yang stacked kemudian next
  7. pada tab presentasi bar distance & cluster distance diisi dengan “0”
  8. pada tab axes widthnya diisi 1pt kemudian next
  9. pada tab number diubah number format settingnya ke number untuk male & female, lalu next
  10. pada tab caption beri nama sesuai dengan keterangan report dalam hal ini populasi manusia.

setelah semua step diatas dilakukan maka hasilnya akan terlihat seperti dibawah ini :

Result

 

 

QlikView


hmm ada mainan baru ni, iseng2 ahh ngoprek.

yuk ah intip dulu dikit, pada pembahasan kali ini lebih mengarah ke Introduction dulu pastinya.

QlikView adalah sebuah tools yang di develop oleh QlikTech pada tahun 1996, pada awalnya QlikView disebut dengan “Quik View” yang mana Quik disini berarti Quality, Understanding, Interaction & Knowledge.

QlikTech sendiri didirikan di 1993 di swedia, dan headquarternya di philadelphia. akan tetapi R&D Departemennya masih di swedia,saat ini QlikView office telah memiliki 1400 karyawan dan 28000 customer yang tersebar di 100 negara.

Qlik management team sendiri rata-rata berasal dari BI development industri yang cukup memiliki nama seperti SAP, Oracle, Siebel, etc.

source visit http://www.qlikview.com/us/company untuk informasi lebih detailnya.

qlikview bukan Business intelegence tools, akan tetapi business discovery tool. fungsinya adalah memaintain perbedaan dari BI Tools lainnya, karena fleksibilitas & menggunakan teknology in-memory associative processing.

sekilas info in-memory technology di qlikview ini berfungsi untuk mencegah ketergantungan BI Tools terhadap koneksi ke Database yang nantinya dapat berpengaruh ke performance database tersebut, technology in memory di qlikview adalah mengambil data dari datasource (dalam hal ini database) kemudian di store di data store qlikview sendiri, jadi apabila kita ingin menampilkan report based on data terakhir collect tidak perlu langsung connect ke sisi database.

contoh penampakannya sebagai berikut :

QlikView Dashboard