December 2006 - Posts

Internet Mati!
28 December 06 01:00 AM | cakriwut | 1 comment(s)

Indonesian

Internet mati! Wah, apa yang salah?
Kalau saja kejadian internet mati terjadi 10 tahun yang lalu, mungkin kita tidak akan terlalu ambil pusing. Mungkin yang pusing, kita-kita yang sudah menggunakan internet di kampus. Tapi dalam beberapa tahun belakangan ini, internet seakan sudah menjadi kebutuhan pokok masyarakat - terutama masyarakat industri dan tentunya orang-orang yang sering bergaul dengan email, chatting, blog, P2P dsb.

Membaca detik.com, telah terjadi kerusakan jaringan bawah laut akibat gempa yang terjadi di Taiwan. Dan masih menurut sumber yang sama, perbaikan akan memakan waktu lebih dari 2 minggu. Waduh, 2 minggu? Seharian ini saja sudah merepotkan apalagi 2 minggu.

Lhoh, kok Taiwan yang mati, kita kena juga?
Jaringan di Indonesia terhubung ke backbone internet melalui network hub yang ada di Taiwan. Dan seperti yang diduga, ada banyak "ternyata" dibalik itu semua.

1. Ternyata, kita tidak memiliki akses ke backbone internet dunia (alias tier-1, kata detik lagi)
2. Ternyata, meskipun ada banyak satelit di atas negara kita, belum ada ring network alternatif
3. Ternyata, kita masih sangat bergantung pada komunitas di LN

1 dan 2 mungkin jauh dari jangkauan kita, tapi 3 ini bisa kita perbaiki.

Saya mencoba melakukan searching via www.google.co.id, hasilnya masih banyak dari network LN - dan bisa diduga semuanya gagal dibuka dengan kondisi seperti ini. Didalam negeri sendiri sudah ada banyak situs, dan hampir semuanya bisa dibuka dengan mudah, namun sangat jarang yang berisi update teknologi (mungkin kalau saya adalah orang BEJ, yang dicari adalah update saham -:)).
Mencari update teknologi dari forum diskusi juga sulit - karena jarang sekali terjadi diskusi di forum-forum teknologi di Indonesia. Diskusi di netindonesia.net sendiri juga tidak terlalu banyak traffic-nya (atau mungkin saya yang salah n tidak mengikuti?). Hmm...

Mungkin kita terlalu malu untuk bertanya... atau mungkin kita terlalu sulit untuk membuat pertanyaan. Kalau orang negeri lain bisa berdiskusi dengan bahasa mereka masing-masing, tentu kita juga bisa melakukannya. Lupakan EYD (khusus yang sudah lulus SMA -:)) - yang penting adalah gunakan bahasa kita sendiri.

Share this post: | | | |

Filed under: General

MOSS 2007: Migration Steps from Beta 2 / Beta 2TR to Final Release
24 December 06 07:16 AM | cakriwut | with no comments

English

Finally, MOSS 2007 had been released and available in MSDN last month. Its about 6 month after beta 2 / beta 2 tr, more or less couple projects using beta version. So now what? Since no upgrades option from beta to final release, then we must migrate it - hoping that we don't need to rebuilt it all over again. Fortunatelly, if you do the migration carefully - all sites will be up so quick.

Migration Steps

The migration process basically is simmilar with fresh installation process. However, in migration we must backup all custom builds, settings and database so we can restore it later.

1. Install .NET 3.0 final release
MOSS 2007 uses .NET 3.0 final release. Before you can install it, any .NET 3.0 beta component must be uninstalled in correct order. I suggest to use uninstall tool from Microsoft. When you run the tools, it will search and uninstall any beta component, including SQL browser component. Stop all MSSQL services to prevent from data disruption. Finally, install .NET 3.0 release and check if the SQL server is running properly.

At this stage, the server will run beta on .NET 3.0 release. Make sure that all sites operates correctly.

2. Copy Any Custom Builds and Settings
Since virtual servers creation are managed by MOSS, then uninstalling the server also deletes the virtual servers and their contents. In this stage, any custom builds and setting must be copied out from virtual server folder. For example, I copied files from bin, custom, and web.config, to tmp folder. You must do this to any site collection that you might have.

 

3. Identify All Databases for current site
MOSS 2007 has several type of database,

• Configuration database, to keep global server settings
• Admin content database, this is basically is a content database but only one for every server
• Content database, this is where all site contents are saved at least one for every web application
• Search database, uses by sharepoint search service
• Shared services databases, uses by shared services provider

We need to keep all Content and Shared services databases - and discard other database type. For example, in the following database system, I keep WSS_Content_* (content database) and SharedServices1_* (shared services database).

4. Uninstall MOSS 2007 Beta
Now we are ready to uninstall MOSS 2007 Beta version (beta 2 or beta 2 tr). Before uninstalling, you can choose to disconnect the server from configuration database - especially when there are two or more servers in server farm. You can skip to disconnect and directly go to uninstallation button from windows add remove programs.

5. Install MOSS 2007 Release
Run setup.exe from MOSS 2007 distribution media and follow the wizards - make sure that you choose server farm installation.
At the end of installation process, Sharepoint Products and Technologies Configuration Wizard window will open. Choose create a new server configuration database, and follow the wizards.

It will creates configuration database and admin site - open the admin site for final configuration.

6. Re-establish All Site Collections
If you are familiar with the beta, then you can start to enable services the server from operations tabs. Then go to Application Management tab to create new web application.

Open your note from step 3, and start to re-create all site collection using their respectives database. The key procedure to re-establish your site collection is that you must specify the same content database. I specify WSS_Content_1282 for my site collection in http://localhost:1282 , etc.

 

7. Re-establish Shared Services Provider
Using Shared Services database (from step 3) - we can restore the SSP into the new system. Goto Manage this Farm's Shared Services and click "Restore SSP".

It will open Restore SSP Page, enter the same SSP database information on the filling form and completes the all other form fill.

8. Restore Custom Builds and Settings
If you have custom builds then this is the time to restore it. Copy all files from backup location to the respective location in virtual directory folder. If you changes/add entry in old web.config, then don't forget to make the same changes/additional entry in new ones on virtual directory folder.

And - done, all sites are now running using final release.

Share this post: | | | |

Filed under: MOSS 2007, Tips and Trick, SharePoint