I apologize to all of you out there for not getting back to the warranty claims thing. I do intend to get back to that line of posts, including more in depth configuration, but my time has been consumed in the infrastructure world of late. Namely, building myself a new virtual server box that can be used for testing. This all sounds pretty easy, but believe me, it’s been far more time consuming than I imagined. My only saving grace is that I blogged a lot tricks a while back that have helped me out of a jam. So today, I wanted to talk about the high level steps it takes to build a new system, using virtual server.
Now, virtualbox is my virtual server system of choice, and I love it. It’s been good. One of the things I love about it is the clone feature. It allows me to take a previous snapshot or current state and convert that into a brand new system. That’s what I’m doing now. I had an ERP 6.0 EHP4 system I’ve been using for development, and now I need one for testing. I thought I had one… but that’s a long story 🙂 Anyway, I chose to clone a snapshot of the EHP4 system before any development work was done. This gave me a good starting point (side note, be careful if you clone a system, then delete it, then try to clone it again. I had a lot of trouble making that work with virtualbox).
Now, once I had my cloned system, it needed a lot of work. First and foremost, it was built on a windows platform, so I needed to get all the updates installed. If you use windows, you know that there are a LOT of updates, especially going back almost 2 years. ha ha ha.The next thing I needed to do is move all of the configuration transports back onto this box. Now a huge deal, but had to wait a while for dropbox to re-synch in order to get everything available, and then one by one, import and install each transport. Next, I need this to be it’s own instance number. Good thing I did a post on that a while ago to remind me of all the steps to do this. However, I was running into issues making it work, so I needed to upgrade the kernel first. Again, good thing I had a post on that too 🙂 Then I thought… well, I should be on Kernel 720, so I upgraded that too. So far so good, but suffice it to say, none of these steps are quick. Now, I want to have this system up to date on all the support packs, particularly related to Web Dynpro, to make sure it can run on as many browsers as possible for testing. I can’t believe how long this takes. It’s been running for nearly 2 days. I guess that’s what happens when you’re 9 – 15 levels down. Oops. Anyway, once this finally finishes, I can run SGEN to compile all the changes and take a virtualbox snapshot. Then I’m finally ready. (of cource… the next mission will be to create another system with Netweaver 7.3. I’m sure there will be posts on that soon).
As always, thanks for reading,As always, thanks for reading and don't forget to check out our SAP Service Management Products at my other company JaveLLin Solutions,