Nothing much going on with me. I’m still trying to kickstart some things with myself and figure out my own workflow for getting things done. It’s coming along slowly but that’s better than nothing. I picked up a Moleskin and started keeping a To-Do list of the simplest things. You know like “Wipe butt after going #2″ or “Remember to pee in the shower while water is running”. Nothing is more embarassing than your wife wondering why there’s dried yellow spots in the bath tube. The list has been going awesome! Totally awesome.

What else? What else?

In early March I went to the orientation meeting for Raleigh’s public access station, RTN. I met this guy Tony there who’s in the process of trying to get some comic and animations off the ground. I told him about some of the stuff I’ve done and we hit it off. We’re now working on some projects together, one of them being a short horror film called Mary. I’ll definitely be posting more about the stuff we’re doing. But that’s pretty much it for now.

There are a few other things I want to post about but think they all deserve their own posts. I’ll get around to those soon…maybe sometime this year. Hopefully. Some of the things I want to post about: Atlanta Supercross, Jax Supercross, Canon XH-1A, Suzuki RM-250 Project, Editing, Shooting Guns, Pimpin’ Ain’t Easy (Yes it is).

Something to look forward to.

The biggest change is the site design. I got tired of looking at the maroon vomit of the last theme. Since I’m not really in the mood to work on a theme from the ground up I decided to use one from WooThemes. I put together a simple logo and poof…finished. Nice and simple I think.

The other change was getting rid of Entrecard. For the past couple weeks my interest in the application has been dying off. As much as I like having people reading the random crap that comes out of my mind, I’m don’t want to over load the site with ads. This isn’t something I’m trying to make money at, it would be nice but still isn’t my goal. Plus I don’t think there is much money to make from ads on a diarrhea posting. Then came the recent Entrecard announcement and the stuff that played out on their forums.  Graham, founder of Entrecard, has proven time and time again the kind of person he is. To put it in the nicest words I know how, the guy is a douche bag. No matter what positive things I was getting out of Entrecard,  I’m not going to support and promote a tool (referring to Graham the tool, not the Entrecard tool) like that.  I fully intend to continue supporting the blogs and friends I’ve made through the service. Hopefully, you will continue reading this blog.

Those are the major changes with the site. I did make some other smalls things but nothing worth mentioning.

I also want to send a HUGE thank you out to the entrecarders that have written recommendations for the site. Every time I get a recommendation I get giddy like a little kid. If my mom lived closer I would probably show them to her like I would when I got an A on a report card…Yeah I’m guessing on that one. I don’t remembering getting any A’s. te he.

I know it’s not a lot but I want to share the recommendations for everyone else and give these guys and gals some link love.

100% Canucklehead approved! Not something to be taken lightly. To say this gent is kinda blogosphere royalty is akin to saying Amy Winehouse kinda like the taste of crack … – Life with Canucklehead

An interesting site .I enjoyed reading the posts and the images are great too.So I highly recommend this one…10 out of 10,for sure.Keep up the awesome stuff – Jesse Blogs It All (Blog no longer exists )

I don’t want to show any favoritism but I will. This one’s my favorite.

You’ve got to see why SIR ROBBIE ROB got an extremely horrible eyesight! I had quite a good laugh reading some of his posts. I admit I am a lurker most of the time and this blog is certainly one of my hangouts. It’s definitely worth every minute being here. You’ve got to see it for yourself! Adding to this blog’s appeal is the zero percentage of declining advert requests. Quick approval on requests and I just love to advertise again and again in this blog! – Lainy’s Musing

I can’t thank all of you enough. Mucho gracias.

Big deal, everyone knows that, you might be saying to yourself. If you think about it, it’s a pretty big deal. A big disgusting deal. Let’s go through an example of why it’s a big deal.

Bob goes to the bathroom to relieve his bladder. He pulls out his little friend and does his business. Once finished he shakes his buddy…one too many times, pretty much masturbating. Then he darts out of the restroom without visiting the sink.

A few minutes later you run into Bob in the hallway. During the normal greetings with Bob, you shake hands. Maybe you even do the handshake followed by the shoulder bump and hand on the back. word. While conversing you happen to wipe your face with the hand Bob shook. Hmmm you like that? Yeah you do.

After this short conversation you go back to your desk to eat that bag of popcorn you just popped. Man…your fingers sure got greasy. Why not lick that butter off your fingers? Yeah like that. Quick question for you…How did Bob taste?

Nasty, right?

Now imagine this same encounter with Bob happening with 10 of your co-workers. You all have something in common…you’ve had Bob’s penis all over you.

Once again, imagine this same encounter with Bob, but instead of him doing a #1 he went #2. Yeah…you’ve pretty much just tossed his salad.

I want you to think about that the next time you go to shake someone’s hand. Most likely they didn’t wash their hands.

If you’re like me, you keep a mental list of the people that don’t wash their hands. Even the ones that “wash” their hands for 4 seconds. Not good enough. I keep the mental list so I make sure I don’t shake that person’s hand. I’m not about to have some guy’s junk all over me without getting dinner first. So yes, it’s a pretty big deal.

netstat –an |grep 389

It won’t give you a ton of information, really just the IP address of the machine requesting information. If you want to get more specific information about the LDAP connections, run a base scope query on the monitoring service.

ldapsearch –D cn=root –w password –s base –b “cn=connections,cn=monitors” objectclass=*

output:

connection=71116 : 192.168.55.171 : 2009-02-18 23:50:00 GMT  : 0 : 1 : UID=WPSBIND,OU=robscomputergarage,c=us :  :
connection=73411 : 192.168.55.165 : 2009-02-19 02:29:58 GMT  : 0 : 669 : CN=ROOT :  :

This information tells us a little more about what’s going on with the connections.

connection=*** is the connection number

xxx.xxx.xx.xxx is the IP address of the client.

yyyy-yy-yy is the date when the connection was first established

zz:zz:zz GMT is the time the connection was made. It also shows the timezone of the connection.

The 0 after the timestamp is showing how many operations are pending

669 is the number of operations that have been completed on that connection

CN=ROOT or UID=WPSBIND is the BindDN making the connection.

The very last field, blank in my example (: :) is the type of connection being made. It’s only valid if SSL/TLS is being used.

Here are the steps I took to change the port the Websphere application used.

1. Login to the Websphere admin console:

https://localhost:9080/admin

2. Navigate to Servers -> Application Servers, choose "server1", then "Web Container", then HTTP Transport

Choose the entry with port 9080. A configuration page will display, change the port here and save.

3. Then navigate to Environment -> Virtual Hosts, choose “default_host”, then host aliases.

Choose the entry with port 9080. A configuration page will display, change the port here (same as above) and save.

Now, restart ITPM (tio stop, tio start) and now you can login using the new port number.

http://localhost:<new port number>/tcWebUI/

ITDS 5.2 & 6.0

ldapsearch -D cn=root -w <password> -b "BaseDN" -s base "objectclass=*" aclentry aclpropagate aclsource entryowner ownerpropagate ownersource ibm-filterAclEntry ibm-filterAclInherit ibm-effectiveAcl

default output:

o=robscomputergarage,c=us
ownersource=default
ownerpropagate=TRUE
aclsource=default
aclpropagate=TRUE
entryowner=access-id:CN=ROOT
ibm-effectiveACL=group:CN=ANYBODY:restricted:rsc:normal:rsc:system:rsc
aclentry=group:CN=ANYBODY:system:rsc:normal:rsc:restricted:rsc

ITDS 6.1 & 6.2

idsldapsearch -D cn=root -w <password> -b "BaseDN" -s base "objectclass=*" +ibmaci

default output:

o=robscomputergarage,c=us
ownerpropagate=TRUE
ownersource=default
aclpropagate=TRUE
aclsource=default
entryowner=access-id:CN=ROOT
ibm-effectiveAcl=group:CN=ANYBODY:restricted:rsc:system:rsc:normal:rsc
aclentry=group:CN=ANYBODY:normal:rsc:system:rsc:restricted:rsc

Starting DB2

When you start ITPM it will fail if DB2 isn’t already running. For whatever reasons, they didn’t include an autostart of DB2 that exists in other products, like ITDS.

Unix
$db2start
You should see the following output if successfully started

11/28/2008 08:32:56     0   0   SQL1063N  DB2START processing was successful.
SQL1063N  DB2START processing was successful.

Windows
From the services window, start the service “DB2 – <instance_name>”
Default service name in ITIO / ITPM 3.1 is “DB2 – DB2-0”

Once you think DB2 is started, you can verify that it is running using the netstat command.
netstat –an |grep 50000 – verify port is LISTENING

DB2 Processes

When DB2 is up and running, you will notice there are a lot of processes that refer to db2 running.

UNIX

db2fmd
db2dasrrm
db2fmcd
db2wdog
db2sysc
db2ckpwd
db2gds
db2syslog
db2ipccm
db2tcpcm
Db2resync
db2srvlst
db2agent (LDAP)
db2fmp
db2agent (TIOINTER)
db2loggr (TC)
db2loggw (TC)
db2dlock (TC)
db2pfchr
db2pclnr
db2event (DB2DETAILDEADLOCK)

Windows

Db2 running on Windows is thread-based (not process-based), so you will only see one db2syscs for all of the instances.

A useful tool is db2_local_ps. It will list all DB2 processes running on a UNIX system.

ITPM’s Connection to DB2

ITPM uses two mechanisms for connecting to DB2. The first one is a established through java using the connection information found in the $TIO_HOME/config/dcm.xml. This file stores the db2 driver path, db2 alias table name, db username, and the encrypted password. ITPM will decrypt the password as needed to establish a connection to the DB. When experiencing connection errors, verify the information in this file is correct.

<config>
<database>
<type>db2</type>
<driver>COM.ibm.db2.jdbc.app.DB2Driver</driver>
<url>jdbc:db2:TC</url>
<name>TC</name>
<username>db2inst1</username>
<password>QJsdAjUEHi8=</password>
</database>
</config>

The other connection uses the J2C Kula user information stored in the Websphere Application Server. You can reference this information though the WAS admin console, navigate to Security -> JAAS Configuration -> J2C Authentication Data. If for some reason you need to update the userID or password to connect to the database, you need to update both the $TIO_HOME/config/dcm.xml and the Kula user.

To test a connection to the database use the following commands. You can run these commands from the command line on a Linux/UNIX system. On Windows you must run these from a db2 command line.

db2 connect to <db_name> user <db_user> using <db_user_password>
example: db2 connect to TC user db2inst1 using password

Useful commands
db2 list tables – lists all tables under schema name you are logged in as
db2 list tables for all – lists all tables in the database (all schemas)
db2 describe table <table_name> – describes table <table_name>

ITPM’s DB2 Tables

TPM utilizes a series of scripts to build its DB2 tables. The directory $TIO_HOME/sql contains all of the scripts. The script that builds the schema is the $TIO_HOME/sql/db2/dbschema.sql. This script is called on every reinit, and will drop and add every table in the database. Use this script to research what the tables look like in the database as well as researching constraint information.

Useful TPM Tables

DCM_OBJECTS – contains a list of all dcm_objects (ID is same in UI). Important dcm_object is ID=0, name=KANAHA which represents TIO (NOT the server that TIO is running on). Hovering over an object will return the object ID stored in this table

PROPERTIES – contains all properties for all dcm_objects. All system wide variables are stored in this table under id=0 (KANAHA)

DCM_OBJECT_WORKFLOW – lists all workflows associated with an object

WORKFLOW4 – contains all workflows ASCII source code (NOTE: There are several associated tables that contain compiled workflow information)

Order of XML Import

When importing an xml file regardless of the order you place objects in your file, objects are loaded in a predefined order. The tool parses the entire file being loaded and populates a data structure such that objects can be loaded in this order. There are a couple of objects that do require a 2 pass technique to be loaded. This is due to the fact that they may contain references to objects further down the list to be loaded. The second pass picks up these few exceptions.

The order of import:

Device Model Category
Device Model
Discovery
RequireDement Specifications
Resource Type Specifications
Address Space
Subnetwork
vlan
customer
ACL
raid-redundancy
storage-function-type
storage-policy-setting
storage-template
Volume-container-setting
SAN
storage-allocation-pool
storage-subsystem
Event-type-specifications
Custom Event Customer
Event Subscription
Power Unit
Switch
Load Balancer
Boot Server
Software Distribution Applications
Software Module
Software Category
Software
Installable package
Software Patch
Software Stack
Cluster Admin Server
Blade Admin Server
Spare Pool
Virtual IP
Software Applications Module
Objective Analyzer Type
Terminal Server
Servers
Monitoring Application
Monitoring Configuration
Group Monitoring Configuration
Virtual Server Template
Logical Cluster
Image
Deployment Plan Template
Deployment Plan
Module
Third Party Software Packages
File Repository
Report Category
SP Service
SP Subscription
Kanaha Config
Cluster Domain

2nd pass
subnetwork
Switch
Storage-subsystem
Server
Load-Balancer

In 6.0 of ITDS, they introduced a proxy server. The main feature of the proxy server is scalability. It does this by distributing directory entries over a set of directory servers, instead of a single server.

I get a lot of requests for setting up proxy servers. I’m finding many of these are due to people having a hard time figuring out IBM’s documentation. To help simplify the process I’m going to show how I configured a proxy server with a back end server in a AIX environment.

In my example, I’m going to have two instances (proxy and back end) on a single AIX 5.3 system and I’ll be using ITDS 6.0 FP7. I start off by creating a instance for the back end, load it with sample data, and then I will configure the proxy.

Configuring the Back End Servers

1. Create the first back end ITDS Instance

idsicrt -I backend01 -e seedforbackend -n

2. Configure the ITDS database

idscfgdb -I backend01 -a backend01 -w password -t backend01 -l /home/backend01

3. Configure the admin DN

idsdnpw -I backend01 -u cn=root -p password

4. Configure a suffix for the environment (I’m using o=ibm,c=us because I will be using the sample.ldif

idscfgsuf -I backend01 -s o=ibm,c=us

5. Import the sample data ldif shipped with ITDS. The ldif is found in /opt/IBM/ldap/V6.x/examples

idsldif2db -I backend01 -i sample.ldif

6. Start the backend server

idsslapd -I backend01

7. Run a quick ldapsearch test

ldapsearch -D cn=root -w password -s sub -b "" objectclass=*

Configuring the Proxy

1. Configure the instance for the proxy

idsicrt -I proxy -e seedforproxy -n

2. Set the admin DN and password

idsdnpw -I proxy -u cn=root -p password -n

3. Set the suffix for the proxy instance

idscfgsuf -I proxy -s o=ibm,c=us -n

4. Now, we need to crypto sync the proxy instance with the back end instance. In my case this is being done on the same server. I will just copy the ibmslapddir.ksf from the backend’s directory to the proxy’s directory. This is a short cut for synching two instances. It also only works when you’re copying the file between servers that are almost the same. Meaning servers that are the same operating system, hardware, etc.

cp /home/backend/idss*/etc/ibmslapddir.ksf /home/proxy/idss*/etc/ibmslapddir.ksf

Listing out the ITDS instances, my environment looks like this:

idsilist -a

Directory server instances:

--------------------------------------
Instance 1:

Name: proxy
Version: 6.0
Location: /home/proxy
Description: IBM Tivoli Directory Server Instance V6.0
IP Addresses: All available
Port: 389
Secure Port: 636
Admin Daemon Port: 3538
Admin Daemon Secure Port: 3539
Type: Directory Server

--------------------------------------
Instance 2:

Name: backend
Version: 6.0
Location: /home/backend
Description: IBM Tivoli Directory Server Instance V6.0
IP Addresses: All available
Port: 1389
Secure Port: 1636
Admin Daemon Port: 3540
Admin Daemon Secure Port: 3541
Type: Directory Server

Next, I need to configure the proxy instance with a global admin group.

5. Start the proxy instance in ‘configuration only mode’

idsslapd -I proxy -a

6. Add a admin member on the backend server. First, create a ldif file with the following:

vi /tmp/globaladmingroupmember.ldif
add:

dn: cn=manager,cn=ibmpolicies
objectclass: person
sn: manager
cn: manager
userpassword: password

Next we need to add this to the backend server.

idsldapadd -p 1389 -D cn=root -w password -f /tmp/globaladmingroupmember.ldif

expected output:
adding new entry cn=manager,cn=ibmpolicies

At this point I need to make an update to the global admin group. This is because cn=root (or local administrators in the ibmslapd.conf file) bind against the proxy server will give administrative access to the proxy schema and proxy configuration only. In order to obtain administrative access to the data in the backend servers you must bind as a global admin group member against the proxy server. This is why it’s important to have global admin group members.

7. Create a ldif file with the following:

vi /tmp/modifyglobaladmingroup.ldif
add:
dn: globalGroupName=GlobalAdminGroup,cn=ibmpolicies
changetype: modify
add: member
member: cn=manager,cn=ibmpolicies

This will make the user cn=manager,cn=ibmpolicies a member of the GlobalAdminGroup group.

8. Add the modifyglobaladmingroup.ldif

idsldapadd -p 1389 -D cn=root -w password -f /tmp/globaladmingroupupdate.ldif
output:
modifying entry globalGroupName=GlobalAdminGroup,cn=ibmpolicies

9. I need to configure my proxy instance to actually be a proxy install. To do this I need to change the server from a RDBM backend to a proxy backend (It will have no database backend).

vi /tmp/changeserver.ldif
add:

dn: cn=Configuration
changetype: modify
replace: ibm-slapdServerBackend
ibm-slapdServerBackend: PROXY

At this point the proxy instance is still in ‘Configuration Only Mode’, so I can a ldapmodify to make the change.

idsldapadd -p 389 -D cn=root -w password -f /tmp/changeserver.ldif
output:
modifying entry cn=Configuration

Note: Pay attention to the port number. This change needs to be made on the proxy NOT on the backend.

10. Add suffix and enable distributed groups
vi /tmp/proxysuffix.ldif
add:

dn: cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration
changetype: modify
add: ibm-slapdSuffix
ibm-slapdSuffix: cn=ibmpolicies
ibm-slapdSuffix: cn=pwdpolicy
ibm-slapdSuffix: o=ibm,c=us
-
replace: ibm-slapdProxyEnableDistDynamicGroups
ibm-slapdProxyEnableDistDynamicGroups: true
-
replace: ibm-slapdProxyEnableDistGroups
ibm-slapdProxyEnableDistGroups: true

idsldapmodify -D cn=root -w password -f /tmp/proxysuffix.ldif
output:
modifying entry cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration

11. Now I need to let the proxy server now about the backend server.

vi /tmp/backendcfg.ldif
add:

dn: cn=backend, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration
cn: backend
ibm-slapdProxyBindMethod: Simple
ibm-slapdProxyConnectionPoolSize: 5
ibm-slapdProxyDN: cn=root
ibm-slapdProxyPW: password
ibm-slapdProxyTargetURL: ldap://backend01.robscomputergarage.com:1389
objectClass: top
objectClass: ibm-slapdProxyBackendServer
objectClass: ibm-slapdConfigEntry

Add the entry into the proxy server.
idsldapadd -p 389 -D cn=root -w password -f /tmp/backendcfg.ldif

output:
adding new entry cn=backend, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory,cn=Schemas, cn=Configuration

12. Add a backend server group for each backend server. In my case it’s only 1.

vi /tmp/servergroup.ldif
add:
pre>dn: cn=serverGroup, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration
cn: serverGroup
ibm-slapdProxyBackendServerDN: cn=backend,cn=ProxyDB,cn=Proxy
Backends,cn=IBM Directory,cn=Schemas,cn=Configuration
objectclass: top
objectclass: ibm-slapdConfigEntry
objectclass: ibm-slapdProxyBackendServerGroup

Add it on the proxy.
idsldapadd -p 389 -D cn=root -w password -f /tmp/config/servergroup.ldif

output:
adding new entry cn=serverGroup, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration

13. The last configuration step is to tell the proxy how the data will be stored across the backends.

In my examples I have three subtrees I need to worry about.
cn=ibmpolicies
cn=pwdPolicy
o=ibm,c=us

Created a ldif file.

vi /tmp/splits.ldif
add:

dn: cn=cn=ibmpolicies split, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration
cn: cn=ibmpolicies split
ibm-slapdProxyNumPartitions: 1
ibm-slapdProxyPartitionBase: cn=ibmpolicies
objectclass: top
objectclass: ibm-slapdConfigEntry
objectclass: ibm-slapdProxyBackendSplitContainer

dn: cn=split1, cn=cn=ibmpolicies split, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration
cn: split1
ibm-slapdProxyBackendServerDN: cn=backend,cn=ProxyDB,cn=Proxy Backends,cn=IBM Directory,cn=Schemas,cn=Configuration
ibm-slapdProxyPartitionIndex: 1
objectclass: top
objectclass: ibm-slapdConfigEntry
objectclass: ibm-slapdProxyBackendSplit

dn: cn=cn=pwdpolicy split, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration
cn: cn=pwdpolicy split
ibm-slapdProxyNumPartitions: 1
ibm-slapdProxyPartitionBase: cn=pwdpolicy
objectclass: top
objectclass: ibm-slapdConfigEntry
objectclass: ibm-slapdProxyBackendSplitContainer

dn: cn=split1, cn=cn=pwdpolicy split, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration
cn: split1
ibm-slapdProxyBackendServerDN: cn=backend,cn=ProxyDB,cn=Proxy Backends,cn=IBM Directory,cn=Schemas,cn=Configuration
ibm-slapdProxyPartitionIndex: 1
objectclass: top
objectclass: ibm-slapdConfigEntry
objectclass: ibm-slapdProxyBackendSplit

dn: cn=o=ibm,c=us split, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration
cn: o=ibmc=us split
ibm-slapdProxyNumPartitions: 1
ibm-slapdProxyPartitionBase: o=ibm,c=us
objectclass: top
objectclass: ibm-slapdConfigEntry
objectclass: ibm-slapdProxyBackendSplitContainer

dn: cn=split1, cn=o=ibm,c=us split, cn=ProxyDB, cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration
cn: split1
ibm-slapdProxyBackendServerDN: cn=backend,cn=ProxyDB,cn=Proxy Backends,cn=IBM Directory,cn=Schemas,cn=Configuration
ibm-slapdProxyPartitionIndex: 1
objectclass: top
objectclass: ibm-slapdConfigEntry
objectclass: ibm-slapdProxyBackendSplit

Add that to the proxy instance.
idsldapadd -p 389 -D cn=root -w password -f /tmp/splits.ldif

output:

adding new entry cn=cn=ibmpolicies split, cn=ProxyDB, cn=Proxy
Backends, cn=IBM Directory, cn=Schemas, cn=Configuration

adding new entry cn=split1, cn=cn=ibmpolicies split, cn=ProxyDB,
cn=Proxy Backends, cn=IBM Directory, cn=Schemas, cn=Configuration

adding new entry cn=cn=pwdpolicy split, cn=ProxyDB, cn=Proxy Backends,
cn=IBM Directory, cn=Schemas, cn=Configuration

adding new entry cn=split1, cn=cn=pwdpolicy split, cn=ProxyDB, cn=Proxy
Backends, cn=IBM Directory, cn=Schemas, cn=Configuration

adding new entry cn=o=ibm,c=us split, cn=ProxyDB, cn=Proxy Backends,
cn=IBM Directory, cn=Schemas, cn=Configuration

adding new entry cn=split1, cn=o=ibm,c=us split, cn=ProxyDB, cn=Proxy
Backends, cn=IBM Directory, cn=Schemas, cn=Configuration

Finally the configuration of the proxy server is complete. At this point I need to start up the proxy in normal mode. Right now, it’s still in the ‘Configuration Only Mode’. It’s also a good idea to restart the ibmslapd on the backend server.

Stop:
idsslapd -I proxy -k
Start:
idsslapd -I proxy

Stop:
idsslapd -I backend -k
Start:
idsslapd -I backend

Wrap Up

Once the backend and proxy instance are running, can you run the following search against the proxy:

ldapsearch -p 389 -D cn=root -w password -b o=ibm,c=us -s base objectclass=*

If you ran the search you would have seen:
ldap_search: Insufficient access
This is because the proxy does not allow cn=root access for anything except for updating proxy schema and configuration. This is the reason we setup the admin

The proper way to run the search would be to use that global admin I created instead of cn=root.

ldapsearch -D cn=manager,cn=ibmpolicies -w password -b o=ibm,c=us -s base objectclass=*
output:

o=IBM,c=US
objectclass=top
objectclass=organization
o=IBM

One of my favorite features in Mac OSX Leopard is the inclusion of Apache and PHP. It helps in getting a environment set up pretty quickly. The only thing that is not included but very important is Mysql. By default Apache and PHP are inactive and need to be enabled by you.

Most of the examples I will show you will be from the command line. I find once you get the hang of working from the command line, everything else is a peice of cake (Mmmmm cake).

PHP

To enable PHP we will need to edit Apache’s configuration file.The file is called httpd.conf and can be found in /etc/apache2/

sudo vi /etc/apache2/httpd.conf

If you need help with vi check out this link

Note: Every time you use the <code>sudo</code> you will most likely be prompted for your system password. Just type it in and hit ‘Return’

Find the following line:

#LoadModule php5_module libexec/apache2/libphp5.so

We need to uncomment out this line. This is done by removing the # sign. It should look like this afterwards:

LoadModule php5_module libexec/apache2/libphp5.so

Save the file and quit.

By default, Leopard has an empty configuration file but provides a file that can be used as a template. From a new terminal window, type:

sudo cp /etc/php.ini.default /etc/php.ini

This creates your php.ini configuration file, located in /etc/php.ini.

PHP is now enabled. We can move on to Apache.

Apache

To start up Apache click on your System Preferences and go to the “Sharing” preference pane and enable “Web Sharing”:

This can also be done from the command line using the apachectl command:

sudo apachectl start

If you need to restart Apache, try this:

sudo apachectl restart

Anytime you make changes to Apache’s httpd.conf or PHP’s php.ini it will require a restart of Apache for the changes to take effect.

Now we can test to make sure PHP works. Create a file (using vi or your favorite text editor) called test.php in your /Users/<username>/Sites/ directory. <username> is the name of the user you’re currently logged it as. In the file, insert the following:

<?php phpinfo(); ?>

Save the file.

Now, open your web browser and type in the address http://localhost/~username/test.php

You should see something like this:

MYSQL

For this part of the installation you will need to head over to MySql’s website and download the latest dmg file.

After downloading the file, mount it and run the installer. After the installation you will was to double-click the MYSQL.prefPane icon. This will install the MYSQL preference pane in the System Preferences, making it easier to stop and start the services.

After you’ve done both, head over to your ‘System Preferences’ and click on the ‘MySQL’ icon and click start.

You can also start MySQL from the command line:

sudo /usr/local/mysql/support-files/mysql.server start

To stop MySQL:

sudo /usr/local/mysql/support-files/mysql.server stop

Configuring MySQL for PHP

The next thing we need to do is make PHP and MySQL aware of each other. In order to do that we will need to change the location of the mysql.sock. The default location of mysql.sock is in the /tmp/mysql.sock directory. This needs to be changed to /var/mysql/mysql.sock as this is where PHP expects it.

Create a my.cnf file in the /etc folder

sudo vi /etc/my.cnf

Insert the following code:

[client]
socket = /var/mysql/mysql.sock

[mysqld]
socket = /var/mysql/mysql.sock

Instead of moving the mysql.sock from /tmp to /var/mysql we will create a link. This is to avoid any possible problems that moving the file could cause with MySQL.

sudo mkdir /var/mysql
sudo ln -s /tmp/mysql.sock /var/mysql/mysql.sock

That’s pretty much it. There are some things I didn’t cover in this post, like PHPmyadmin and Virtual Directories, but I will cover at a later time. I wanted to give you the least amount of steps needed to get up and running.

Before you start installing and applications I would recommend setting a password for MySQL’s root user. By default this is blank.

To change the password:
$ mysqladmin -u root password NEWPASSWORD

Resources

Here are some links I would recommend checking out. Many of them only covering one specific component of the Apache, PHP, and MySQL setup.

Installing MySQL on Mac OS X – MySQL’s guide to installing on OS X

Foundation PHP

Apache’s httpd documentation

PHP.net