Friday, September 17, 2010

Websphere portal server and Lotus Web Content Management performance tuning tips

an illustration of a plunge poolImage via WikipediaIf you have had the pleasure to install and set up a WebSphere Portal environment, you know that sometimes it can be a big, fat bloated piece of something you'd expect from Redmond.

You will probably see the biggest increase from the Base portal tuning recommendations.
Give it as much memory as you can spare and increase the thread pool size -- you should see performance increase just from this. (If on Windows, you can't go above 1.5G, but for a server Windows should always be your last choice.)

After the base portal tuning, try again, then start to do some performance monitoring.
If you're a big WCM user, check the caches here and make them bigger.

  • a starting point is IBM doc#swg27007059,
    IBM WebSphere Portal Performance Troubleshooting Guide,
    it contains basic generic troubleshooting methodology. You may want a methodology like this for your manager or client.. Also a step-by-step guide to the PMI / Tivoli Performance Viewer -- these are definitely worth checking to get basic measurements of your server.
Patches (aka fixpacks) sometimes fix performance issues. I haven't encountered one specifically, but it has been known to happen.

Also testing Zemanta with this post.. the included image is totally unrelated.
Actually, I said 'pool' -- I think that's where it came from, and you have to admit it looks cooler than a 'websphere'.
Enhanced by Zemanta

Friday, September 3, 2010

Connect a device directly to your macbook with ethernet (for filesharing between computers or to configure for wireless)

This is what I did specifically for my Brother HL-2170w laserprinter in order to get it configured for wireless use. I couldn't use the automatic configured because I have a key on my network.

If you are using wireless at home, and you want to configure something like a wireless printer, you will first have to hook it up 'wired'--that is, via Ethernet. You can connect it directly to your router, but in my case the router is in the basement and not where I want my printer to be--it's easier to move my laptop.

This can also be used to connect another laptop up to your system without a router or hub between them. You can connect directly with just an ethernet cable, because the Mac (at least newer ones) have auto-sensing ports. This can be used for faster/secure file transfer, as well as giving the other laptop access to the internet by sharing your connection in the following cases
  • other laptop doesn't have a wireless
  • you don't want to share the key/password for your network
  • you want to observe the traffic of the other computer for research or forensic purposes (make sure you have consent of the parties)
  • you have a 3G, cellular network, or other network connection that the user can't connect to
  • any other reason you want to share
It was fairly straightforward for me because I have plenty of past experience with dhcp servers, routers and TCP/IP routing. If you don't, it may seem like magic. Best of luck.

The key thing is starting the dhcp server; this allows the other machine to get an IP address allocated automatically from you (and routing information, if you are doing connection sharing). The alternative is manually configuring the IP address manually, often more trouble than it's worth, and not an option for many wireless devices like printers.
  1. Open sharing settings in System Preferences
  2. Highlight the Internet Sharing selection on the left but don't click the checkbox yet; this will show the options on the right.
  3. Select the interface that has the connection you want to share (the one that you are using, e.g. wireless) from the pulldown
  4. To computers using: Ethernet
  5. Click on the 'internet sharing' check box and click Start in the ensuing dialog box.
(Here's a page with screenshots; it's from OS X 10.4, and some of the screens have changed.)

'Internet sharing' turns on a dhcp server and enables routing.
Note: that a 192.168.2.X network is used for sharing by default; you can find the rules that OSX uses in the 'man InternetSharing' entry (and you can change SharingNetworkNumberStart)--more info on this Mac OS X Hints page, be sure to read the comments.

This connection sharing can be used for more advanced scenarios as well.
Say you and a friend are on wireless, but different networks (they could be public and private, or wifi and tethered via cell phone).
You could send some traffic via one interface, and others via the other. This can be very useful to network professionals for troubleshooting.
(I usually use a squid proxy on a separate host, sometimes through an ssh tunnel, with a customized .pac proxy auto-config file; more on that later..)