I have experienced some difficulties install Siebel on Windows platform, I started by trying the installation on Windows 2008 where I saw several articles confirm the supportability of this OS.
I all my trials has failed successfully :) the failure is because many reasons
The installation process itself is complicated (
1- Download Sources.
2- Extract Sources
3- Compiling the extracted sources into Executable
4- Installing the Siebel Components
5- Configure Siebel Components.
Actually, what makes the process complicated is not the number of the steps, the problem is it seems that the Java application used are not compatible with the latest OSs; although it works but if there is missing files, it never complains, it continue peacefully without telling you about it, and you stuck in other stages.
So, the best thing your can say here “if you start correctly, you will end successfully”, that’s the reason I am posting this, so start by 1st process and ensure it is successful by downloading the correct sources even though you have a limited connection and it may take days to download (19 GBytes for Siebel 8.0.0 and 13 Gbytes for Siebel 8.1.1).
So here is the list of files you (have to) download in case you want to have normal (not selective) deployment.
For Siebel 8.0.0 those are the files I have downloaded and lead to successful deployment.
| Size in bytes | File name |
| 655,344,135 | B34835-01_2of7.zip |
For Siebel 8.1.1 those are the files I have downloaded and lead to successful deployment.
| Size in bytes | File name |
| 426,190,173 | V14474-01.zip |
In this article, I have used one of the HP uCMDB features to create additional CIs based on the discovered data on certain CI
Scenario:
Operators want to display Operating System name as CI linked with Node CI
Steps:
1-Create New CIT for the Operating System
2-Create relation between Operating System CIT an d Node CIT
3- Create Correlation Rule
3a- in Query Mode adding your Searching criteria TQL
3b- in Enrichment Mode add the CIT you want to create
3c- Add Query Node Definition (How the new CI Attributes will be populated)
4- Create Scheduler task to run the Enrichment Rule
Under Modeling > CI Type Manager right click the CIT tree and create a new CIT
I recommend to create the CIT under NodeElement CIT to inherit all the relations and configurations as all NodeElement child CITs
Note: Remove ABSTRACT_CLASS from Type Qualifiers to be able to create CIs
2-Create relation between Operating System CIT an d Node CIT
Select Node CIT and OS CIT and right click select Add/remove Relationship.
Move to Modeling > Enrichment manager and create new rule
In Query mode
I will Edit the Query Node Properties and filter my TQL
I will select DiscoverOSName is Not Null to ensure that this will apply to only nodes that Has this attribute populated
Change the Operations to Enrichment Mode and add the operating System CIT, and Add the relation between Node CIT and Operating System CIT
Fill the Operating System attributes as needed.
for Name attribute use the option By Attribute and select Node CIT and DiscoveredOsName
Note: You may create combination of Node attributes as a value by choosing Advanced
Go to Administration > Scheduler
Create New Schedule
Add Run an Enrichment Rule
Select your schedule
Run the schedule
The Outcome will be like this, create a view to with Node and OS CITs to get the result.
Create New View or Modify the current view.
Add Node CIT
In the Hierarchy pane, right click Node CIT and select Add Group by Attribute
Select DiscoveredOSName as Group by
This is a preview on How it should look like.
My friends, Here I am sharing Google+ invitations feel free to click on the link below and join the revolutionary Social Network.
https://plus.google.com/_/notifications/ngemlink?path=%2F%3Fgpinv%3Dc8uQdNiqprg%3Am0TQQkh_nGQ