Installing Oracle 11r2 on Windows 2008R2 Server Part 2

Hi,

Welcome to Installing Oracle 11r2 on Windows 2008R2 Server Part 2 of the series

Doing a Complete install of Siebel 8.2.2.4 on Oracle 11 r2, Win 2008R2. All from Scratch

In this part we will configure an oracle database server. This server will house a development database, and a test database. This walkthrough will focus only on the development database installation.

To Install an Oracle database we will go through the following steps

  1. Install the Oracle Database Software This was completed in Part 1 Here
  2. Configure the Oracle Database
  3. Configure the Listener
  4. Verify & Configure Windows Services
  5. Configure Windows Firewall
  6. Do Connectivity Tests

To Configure an oracle database you need to run the dbca from a command prompt. Follow the screenshots, and step guide below to configure the database for use as a Siebel development server.

We need to install a Custom Database, as we need to configure advanced properties. Hit Next

Continue reading “Installing Oracle 11r2 on Windows 2008R2 Server Part 2”

Installing Oracle 11r2 on Windows 2008R2 Server Part 1

Hi,

Welcome to Installing Oracle 11r2 on Windows 2008R2 Server Part 1 of the series

Doing a Complete install of Siebel 8.2.2.4 on Oracle 11 r2, Win 2008R2. All from Scratch

In this part we will install an oracle database server. This server will house a development database, and a test database. Production servers should generally not be deployed on the same database as development, but the installation of the test server demonstrates that it is possible, this walkthrough will focus only on the development database installation.

Before we begin prepare the Oracle Server by doing the following steps:

  • install win 2008r2 operating system
  • join domain
  • update operating system with latest patches
  • install your favorite tools (mine are notepad++, procmon from sysinternals and winrar)

To Install an Oracle database we will go through the following steps

  1. Install the Oracle Database Software
  2. Configure the Oracle Database
  3. Configure the Listener
  4. Verify & Configure Windows Services
  5. Configure Windows Firewall
  6. Do Connectivity Tests

I’m still doing the writeup of the actual installation, for now, if you do the installation – run an install software only with no starter database.

Read the Next part in the series “Configure the Oracle Database” 

Enjoy!

/Henrik

Doing a Complete install of Siebel 8.2.2.4 on Oracle 11 r2, Win 2008R2. All from Scratch

Hi,

This is going to be a looong series of posts. I needed to install a new development environment, and I wanted to test the new Siebel 8.2.2.4 SIA with all the verticals available.

Installing Siebel is no small task, and this guide is not meant to be a full replacement for reading up on the procedure on supportweb (My Oracle Support) MOS, including installation guide in bookshelf, release notes, post installation information, bugs and what-have-you-not, I’ll do my best to link to the different documents that may be relevant along the way.

The Installation will Guide you through:

It will not:

  • Teach you to install windows 2008R2

I’ll assume the following, that you in advance prepare and install two Windows 2008R2 servers in a domain. I use Hyper-V services, its fast and effortless to get started on the deployment for a new development environment.

Lets Get Started, We will do the Oracle database first!

Read About the Installation of the Oracle Database here: Installing Oracle 11r2 on Windows 2008R2 Server Part 1

I´ll finish the writeup for all the bits and pieces over the next few weeks, and publish them as i get the time. Let me know if you have any comments!

Enjoy!

/Henrik

Using Subversion with Siebel Tools

I’ve for as long as i can remember been using SourceSafe integration for all my siebel projects. Thats all good and fine, but it is aging, and for other projects I’m now using subversion. So when i installed a complete siebel 8.2.2.4, i decided to move the source control integration from SourceSafe to SVN.

First off, Siebel is not really heping you here, the default source control file installed with 8.2.2.4 looks like the source control file back in Siebel 6.

Researching a little on the net, provided lots of discussions if siebel can integrate with SVN, and the answer to that question is yes – it can. But if you come from a development background that is non siebel, then I might as well call it as it is, the source integration will only cover objects modified directly in tools, and it is solely a change log, allowing you to backtrack changes in time to a specific object. Its not a build repository, or even a complete picture of the changes that may be within one version of Siebel (ie. non-metadata changes are not included).

The batch file srcctrl.bat needs a lot of modification to work, luckily there was this one guy Michael Williams, who posted a good looking svn enabled srcctrl.bat file.

Use the file below as your starting point.

@echo off 
SETLOCAL
set SOFTWARE=svn
set CHECKIN=%SOFTWARE% commit
set CHECKOUT=%SOFTWARE% checkout
set ADD=%SOFTWARE% add
rem ==================================================================
rem =============== User defined parameters ==========================
rem ==================================================================  
rem IF SVN IS NOT IN THE DEFAULT PATH ADD IT HERE set PATH=[Path_to_svn];%PATH%
set SVN_URL=https://[svnserver]/svn/[repository]
set SVN_REPOS=[trunk]
set SRC_USR=[youruser]
set SRC_PSWD=[yourpassword]
set LOGFILE=[path_to_siebel_root]\SVN\[repository]\svn_integration.log
set WORKING_DIR=[path_to_siebel_root]\SVN\[repository]
rem LOGFILE SHOULD NOT HAVE SPACES IN ITS PATH 
rem AND WATCH OUT FOR TRAILING SPACES ON THE SET COMMANDS! 
rem ================================================================== 
rem ==================================================================     
set OPTIONS=--username %SRC_USR% --password %SRC_PSWD%
set COMMENT=-F
set FILE=
echo ===========================START============================ >> %LOGFILE%   
echo %DATE% %TIME% >> %LOGFILE%   
echo ARGS: >> %LOGFILE%   
echo %* >> %LOGFILE%
echo ============================================================ >> %LOGFILE%   
echo PARSING.. >> %LOGFILE%   
set ACTION=%1
shift 
set DIR=%1
shift
set COMMENT=%COMMENT% %1
set COMMENT_FILE=%1
shift
set FILE=%1
SET DIR_NO_QUOTE=###%DIR%###
SET DIR_NO_QUOTE=%DIR_NO_QUOTE:"###=%
SET DIR_NO_QUOTE=%DIR_NO_QUOTE:###"=%
SET DIR_NO_QUOTE=%DIR_NO_QUOTE:###=%
if errorlevel 100 goto END   

echo ACTION: %ACTION% >> %LOGFILE%   
echo DIR: %DIR% >> %LOGFILE%   
echo COMMENT_FILE: %COMMENT_FILE% >> %LOGFILE%   
echo FILE: %FILE% >> %LOGFILE%   
echo DIR_NO_QUOTE: %DIR_NO_QUOTE% >> %LOGFILE%   
echo ============================================================ >> %LOGFILE%   

if %ACTION%==checkout goto CHECK_OUT 
if %ACTION%==checkin goto CHECK_IN   

:CHECK_OUT 
echo =========================CHECKOUT=========================== >> %LOGFILE%   
echo Check out file: %FILE% from Source Control System >> %LOGFILE%   
echo Change local directory to %DIR% >> %LOGFILE% 
chdir %DIR% >> %LOGFILE% 2>&1   
echo Start checking out %FILE% from Source Control System >> %LOGFILE% 
echo %CHECKOUT% %SVN_URL%/%SVN_REPOS% %OPTIONS% "%WORKING_DIR%\%SVN_REPOS%" >> %LOGFILE% 
%CHECKOUT% %SVN_URL%/%SVN_REPOS% %OPTIONS% "%WORKING_DIR%\%SVN_REPOS%" >> %LOGFILE% 2>&1   
echo ======================CHECKOUT DONE========================= >> %LOGFILE%   
goto END   

:CHECK_IN 
echo =========================CHECKIN============================ >> %LOGFILE%   
echo Check in file: %FILE% into Source Control System >> %LOGFILE%   
echo Change local directory to %WORKING_DIR%\%SVN_REPOS% >> %LOGFILE% 
chdir %WORKING_DIR%\%SVN_REPOS% >> %LOGFILE% 2>&1   
if exist %FILE% goto FILE_EXIST >> %LOGFILE% 2>&1   
echo Copying %FILE% to local Working Copy Folder: %WORKING_DIR%\%SVN_REPOS% >> %LOGFILE% 
copy "%DIR_NO_QUOTE%%FILE%" "%WORKING_DIR%\%SVN_REPOS%\%FILE%" >> %LOGFILE% 2>&1   
echo Add %FILE% in case it doesn't exist in Source Control System >> %LOGFILE% 
echo %ADD% %WORKING_DIR%\%SVN_REPOS%\%FILE% %OPTIONS% >> %LOGFILE% 
%ADD% %WORKING_DIR%\%SVN_REPOS%\%FILE% %OPTIONS% >> %LOGFILE% 2>&1
goto COMMIT   

:FILE_EXIST   
echo Copying %FILE% to local Working Copy Folder: %WORKING_DIR%\%SVN_REPOS% >> %LOGFILE% 
echo copy "%DIR_NO_QUOTE%%FILE%" "%WORKING_DIR%\%SVN_REPOS%\%FILE%" >> %LOGFILE% 
copy "%DIR_NO_QUOTE%%FILE%" "%WORKING_DIR%\%SVN_REPOS%\%FILE%" >> %LOGFILE% 2>&1
:COMMIT 
echo Check in %WORKING_DIR%\%SVN_REPOS%\%FILE% into Source Control System >> %LOGFILE% 
echo %CHECKIN% %WORKING_DIR%\%SVN_REPOS%\%FILE% %COMMENT% %OPTIONS% >> %LOGFILE% 
echo ***** COMMENT_FILE ***** >> %LOGFILE% 
type %COMMENT_FILE% >> %LOGFILE% 2>&1 
echo . >> %LOGFILE% 
echo ************************ >> %LOGFILE% 
%CHECKIN% %WORKING_DIR%\%SVN_REPOS%\%FILE% %COMMENT% %OPTIONS% >> %LOGFILE% 2>&1
echo =======================CHECKIN DONE========================= >> %LOGFILE%   
goto END   
:END 
echo %DATE% %TIME% >> %LOGFILE%   
echo ============================END============================= >> %LOGFILE%
ENDLOCAL

Replace the elements in [square brackets] in above file, and you are ready to go.

I Use Subversion 1.7.x, SVNServer (std Edition) and Siebel Tools 8.2.2.4

Note: Rename the source control batch file (eg. to svn_srcctrl.bat) as siebel will overwrite the srcctrl.bat file on patches and updates 🙁

Enjoy!

/Henrik

Welcome to the New Home of Manzana on the web

Today we completed the upgrade of the software that drives Manzana’s webpages, at the same time we migrated the database.

While we had the editors open we changed the design of the webpage towards a more one-page design, we hope you like it.

We know there are corners that still needs dusting, cleaning up, and updating – we will get around to this one of the coming Christmas days 🙂

Meanwhile enjoy our new webpage, and we wish you a Merry Christmas from Manzana

/Henrik

Running Shallow

A new year is approaching fast, and the last remaining days of 2003 are hastily passing by, leaving time for family and for those involved in Siebel Projects, a well deserved chance to think about something else than Siebel Best Practices, Screens, Views, BusComps, user interface, Integration design, EIM processes and all the other what-have-you-nots of a typical Siebel Project. There are times when even the best running Siebel project is running shallow, and the resources that comprise the team are just on the verge of wearing thin. This is normal in all larger-scale projects and its not a foreign concept in a Siebel project. There are many ways to deal with this challenge in a project team – right this season the re-vitalization of the Christmas holidays is the obvious and easy one – simply ask team members to not think about the project for the holidays…. But there are other things you may want to look into too (after all Christmas is only once a year);

  • Look at the team groups;
    • Are they communicating on the same level.
    • Do they combine efforts to make team progress.
    • Are team member only concerned with progress on their own area of responsibility.
    • Are team members actively discussing issues and solutions.
    • Are all team members being involved in the discussions.
    • Are the team members understanding the business reasons for the solution requirement.
    • Do the team make forward-moving decisions – and stick with them.
    • Is the team asking for help and input when facing challenges.
  • When you’ve looked at the above points, you probably have some notion if you need to change anything to make the project run better. Here’s a list of steps you could take to make your project teams run even smoother;
  • Shuffle members between teams in order to bring fresh thinking and new perspective into a team, if you identified a weakness or deficit on a team, look for a new member that excels in those areas. Don’t present changes as demotions or promotions, but rater as adding catalysts in order to help teams become even more successful. Their success is the projects success.
  • Encourage “eXtreme Programming” in the teams when they are being challenged, even though extreme programming methodology is developed for pure programming tasks, it is easily adapted for Siebel Development. Encourage that extreme programming teams are sought across all teams. If you want to know more about extreme programming then read the book “eXtreme Programming eXplained” by Kent Beck.
  • Encourage discussions about solutions, but make sure that everybody have the business reasons for the solution requirement clear in memory. Try and provide the teams with simple clear cut business reasons and requirements, just the headlines. This will allow teams to develop a better solution, without discussions creating divergence between customer requirements and resolution.
  • Encourage taking mental breaks from the project. both in the weekends, but also during lunch breaks, and in the evening. Sometimes the distancing from the challenges in the project will allow a fresh take on any challenges that a team and it’s members may be facing.

In Manzana we live on our customers’ success, and our ability to scope, develop, implement and rollout solutions that cover the above points and more. And the results speak for themselves. Our customers are satisfied, their employees are satisfied, and resources have been freed for more important tasks. Look at the Customer Success to see some quotes from customer installations that Manzana have built.

Further we pride ourselves in not just being an implementator of Siebel, we also use Siebel actively in Manzana. So our experience also comes from our own daily use of Siebel.

Thanks for your time!
Henrik Ohm Eriksen, CEO
Manzana

If you are considering a CRM or Siebel solution or just want to ask a question, then send us an email and we will get back to you asap. If you would like to inquire on hiring Manzana Services please do not hesitate to contact us, either by email or phone.

And also, we highly recommend you visit the Siebel Inc. homepage at www.siebel.com

Planned outage on Tuesday the 26. of februar 2013 from 01:00 to 08:00

There is a planned outage of Manzana’s internet connection on Tuesday the 26. of februar 2013 from 01:00 to 08:00, due to an upgrade at Manzana’s internet provider.

This means that in the above period it may be impossible to reach our web servers.

Siebel Error Codes

Siebel use two kinds of error codes the XXX-XXX-nnnnn (eg. SBL-DAT-00402) type, and the internal ones in the e object thrown in code. I Can’t find a list of these internal error codes, and the SBL-XYZ-123435 codes, are not readily available in code unless you string parse, ofcourse… So I need the mapping to the error objects errCode.

I need to remember these things so for my own reference I added this post, I will update it as more errorcodes are determined by me.

SBL-DAT-00225, e.errCode = 27546 (Value does not exist in bounded picklist) – thanks Tuba !

SBL-DAT-00381, e.errCode = 27714 (Duplicate Record Exists, User Key Violation)

SBL-DAT-00382, e.errCode = 27715 (Duplicate Record Exists, Unique Index Violation)

SBL-DAT-00402, e.errCode = 27735 (This operation is not available for read only field)

SBL-DAT-00523, e.errCode = 27864 (The selected record has been modified by another user since it was retrieved), Race Condition on BC.WriteRecord()

SBL-???-?????, e.errCode = 28378 (Raise Error text), the raised text is in e.errText

SBL-EXL-00147, e.errCode = 27515 (BC.SetFieldValue() targets a field which is not active)

SBL-EXL-00119, e.errCode = 28461 (BC.GetFieldValue()), the Field is not activated, do not exist in BC

SBL-EXL-00109, e.errCode = 28511 (PropertySet Data is Binary), On PropertySet.GetProperty()

If you have more information, leave a comment!

/Henrik Ohm Eriksen