If you want to get the whole saving/investing thing started early, I would just toss the money in a set of index funds. I recommend Vanguard (low fees and high quality product - index funds are more or less all the same), diversifying across a few different indices (depending on what you wish, you could spread it across the S&P500 fund, the international equity fund, a corporate bond fund, and treasuries).
AFTER THAT, I would then begin the "learning" phase. What most people do not understand is that putting your money in a few companies is unbelievably risky unless you really know what you're doing. You can't just invest in names you know, the key is how much you're paying for them. With your money tied relatively safely in index funds, I would start researching individual companies. Take a look at the Investor Relations section of their websites, and read through the most recent 10-K. Don't worry if its unbelievably confusing, it's honestly not meant to be fully understandable by the general public. Your first time through, look through the verbal parts. Read the sections that describe the business, read sections like the Management's Dicussion and Analysis - skim through some of the numbers if you wish. Watch, if you have access, financial news programs, the Wall Street Journal, finance sections of news websites like CNN. Go to Yahoo! Finance or similar sites and see what the recent news is for specific companies as well as the economy as a whole, and look at how this news is impacting stock prices. Use Investopedia and Wikipedia.
What's important that this stage is that you learn. Avoid getting trapped into the world of people who have never opened a 10-K but think they're stock market geniuses because their uncle's brother's friend's barber had a great stock tip. One really good thing to do once you get into college is go to the business school library if there is one and ask how you can get access to equity research reports of companies. I would recommend that, at all costs, avoid technical analysis. It's an interesting idea but at the retail level (what you and 99.9% of the rest of the public is at), it's just not a very good idea.
http://www.investopedia.com/
http://www.capitalmarket.com/
http://www.commodityinsights.com/
www.stockclever.com
http://www.stockstobuy.co.in/
www.maketheprofit.com
http://www.finance-trading-times.com/
http://sharegenius.blogspot.com/
http://www.moneycontrol.com/
Wednesday, August 11, 2010
Sunday, July 25, 2010
Siebel Application Object Manager
Siebel Application Object Manager (AOM)
Application Object Managers (AOMs) host the Business Objects layer and Data Objects layer of the Siebel architecture.
It is a server component that creates and processes data at multiple levels.
UI layer (supported by the Siebel Web Engine)
Business object layer
Processes business logic
Data object layer (supported by Data Manager)
The AOM is used primarily to support Siebel Web client connections.
AOMs are hosted as components in the Siebel Server and run on the application server (the machine that hosts the Siebel Server). The Siebel Server provides the infrastructure for an AOM to serve multiple Siebel Web client users. Multiple AOM components can run on a single Siebel Server installation.
AOMs communicate with clients using the TCP/IP protocol through a Web server that contains the Siebel Web Server Extension plug-in (SWSE). Communication between the Web server and the AOM can be compressed and encrypted. An independent session is established to serve incoming connect requests from each client. Subsequent requests from clients are directed to the same AOM tasks until the sessions are terminated.
After startup, AOMs do not achieve their full run-time environments until after the first connect, therefore, leading to possible delays during the first connection.
Application Object Managers (AOMs) host the Business Objects layer and Data Objects layer of the Siebel architecture.
It is a server component that creates and processes data at multiple levels.
UI layer (supported by the Siebel Web Engine)
Business object layer
Processes business logic
Data object layer (supported by Data Manager)
The AOM is used primarily to support Siebel Web client connections.
AOMs are hosted as components in the Siebel Server and run on the application server (the machine that hosts the Siebel Server). The Siebel Server provides the infrastructure for an AOM to serve multiple Siebel Web client users. Multiple AOM components can run on a single Siebel Server installation.
AOMs communicate with clients using the TCP/IP protocol through a Web server that contains the Siebel Web Server Extension plug-in (SWSE). Communication between the Web server and the AOM can be compressed and encrypted. An independent session is established to serve incoming connect requests from each client. Subsequent requests from clients are directed to the same AOM tasks until the sessions are terminated.
After startup, AOMs do not achieve their full run-time environments until after the first connect, therefore, leading to possible delays during the first connection.
Monday, July 19, 2010
Escript Best Practices
There a Golden Rule that every Siebel Developer should follow when it comes to scripting. This golden rule is to never script unless there is no other choice on meeting your requirements. Scripting is the highest level of customization and adds complexity and cost to the configuration. So scripting should be your last resort. So the first practice is to avoid script. So to avoid scripting, below are some configuration methods every developer should think before attempting to work with eScripts
User Properties: This is a major feature in Siebel. An example of this is “On Field Update Set”. This is used instead of scripting on Set Field Value event to change some other value.
Calculated Fields: Calculated fields come very handy when we need to do validation. With the help of Calculated Fields and User properties lot of functional requirements are achieved.
State Models: State models help in restricting transitions from one field value to other. So there is no need to script to check the status change.
Runtime Events: This was introduced in 7.7 and has been of significant help to the developers to on invoking Workflows & Business Services based on events. So avoid Business Component events.
Workflows: Instead of writing a big script, we can break that down to a series of workflow steps. We have steps Like Write, Update, if condition, Sub-Process, Invoke Business Service and lot of other key stuff. Workflows are very efficient and promising.
User Properties: This is a major feature in Siebel. An example of this is “On Field Update Set”. This is used instead of scripting on Set Field Value event to change some other value.
Calculated Fields: Calculated fields come very handy when we need to do validation. With the help of Calculated Fields and User properties lot of functional requirements are achieved.
State Models: State models help in restricting transitions from one field value to other. So there is no need to script to check the status change.
Runtime Events: This was introduced in 7.7 and has been of significant help to the developers to on invoking Workflows & Business Services based on events. So avoid Business Component events.
Workflows: Instead of writing a big script, we can break that down to a series of workflow steps. We have steps Like Write, Update, if condition, Sub-Process, Invoke Business Service and lot of other key stuff. Workflows are very efficient and promising.
Best Practices of Scripting in Siebel
This article presents a collection of Siebel scripting best practices.
1. Always use TheApplication to call the application, as the declaration of a global variable to represent the application (e.g. var theApp = TheApplication()) is not recommended by Siebel. The use of this variable may cause memory leaks, reduce performance or other unpredictable behaviour.
2. User-defined functions must be Forward Declared in the general declarations of each script. This avoids compilation errors that may arise if the functions called are not in alphabetical order. The compiler compiles all functions alphabetically and so if one function calls another that is later in the alphabet the compiler does not recognize this second function and therefore, fails.
3. Be cautious when adding script to business components as this code applies application wide across applets and views. If a certain piece of coding is needed at the business component level but is restrictive to certain situations like if exposed only through some particular views then make sure to limit the processing through an appropriate condition.
4. The use of 'With' is recommended by Siebel as it enables the code to be changed faster and more readable way to group operations performed within the same business component. The use of 'With' also presents a slight performance improvement.
5. Using variables can make code maintenance easier due to readability. However overuse of variables increases the amount of operations that have to be performed and can reduce performance slightly.
6. Siebel does not recommend the use of 'Empty'. 'Empty' is an undefined variable which is assigned as type variant. A variant is initially set to a null string (''), which means that any scripts currently using this term will not be affected. However, it is better practice to assign '' rather than 'Empty' to any strings you need to set back to NULL. The use of 'Empty' prevents Option Explicit from checking all other variables are declared correctly.
7. The use of 'ActivateField' prior to a query is the equivalent to the 'SELECT' statement in SQL. The use of 'ActivateField' in Siebel scripts code can be confusing and should be minimized as much as possible as this has a performance impact. However there is nothing worse than receiving a runtime exception: ' was not active...'. When activating fields note that:
a. Siebel system fields (Id, Created, Created By, Last Updated, Last Updated By) are always force active.
b. Fields that have Force Active = Y on the business component are always force active.
c. Fields that have Link Specification = Y on the business component are always force active.
d. Fields that are included in the definition of an applet on the active view if it is bound to a web template item and the 'Show In List' property of the list column or 'Visible' property of the control is TRUE. If the user removes the list column from the 'Columns Displayed' in the list applet, the field may no longer be active after the next query.
e. Fields that are used as part of a calculated field calculation when the calculated field is retrieved for use on the active applet.
8. 'ActivateField' should only be used prior to 'ExecuteQuery' to ensure that a particular field will be activated and included in the equivalent 'SELECT' statement of the query. Therefore 'ActivateField' is usually never to be used with 'this'/'Me' (eg. this.ActivateField('Field1')). This is because you don't usually perform a query in the current context as this would change the on screen query displayed to the user. Siebel actually specifies that the use of ActivateField with 'this' can possibly cause data corruption to occur.
9. When performing a query, always use 'ForwardOnly' after the 'ExecuteQuery' to set the cursor position unless moving back through the returned records. This is a much faster query because it does not create a cache that stores the previous records.
10. If you have a set of 3 or more 'IF Else If' statements then use 'Switch Case' statements instead. This simplifies code and improves performance.
11. It is best practice in Siebel scripting to use the 'Try/Catch/Finally' statements in code. This will ensure that exceptions are caught and handled appropriately and instantiated object variables are always destructed in the finally block (which reduces the chances of memory leak) as the code in the finally block is always executed. Note that object variables should be destroyed in the reverse order they were instantiated.
12. Reduce the number of queries performed as much as possible. Siebel maintains the parent-child relationships defined in links automatically so there is no need to query the child Business Component to obtain records for a given parent. Make use of commands like, 'GetParentBusComp' to access the parent record, instead of re-querying to retrieve record.
13. Don't create objects (BC and BOs) if you need a reference to BC and BO from the current context. Make use of default application variables 'BusComp' and 'BusObject' in this situation.
14. The use of 'ActiveBusObject', 'ActiveBusComp' and 'ActiveApplet' should be limited because the object represented by these statements may change depending on the active applet. Siebel recommends the use of the 'this' object for eScript ('Me' for Siebel VB) wherever possible. 'Me'/'this' represents the object where the code is written, 'ActiveXXX' represents the object behind the current active applet. The use of 'Me'/'this' is a safer method, especially during development when, it is not entirely clear which applet will be active at any given time. It also enables easier interpretation of the scripts because the 'base' object, represented by 'Me'/'this' will never change. The use of 'Me'/'this' also removes the need to store the active BusObject and active BusComp in variables as it does not need to be declared or explicitly destroyed at the end of the function.
15. All code must be indented logically, including comments which efficiently describe what the script is doing. Each new script should include a header comment which provides: Author, Date, Description and Version History for that script.
16. Delete all 'empty' scripts that once contained text. Delete everything, including the function header and footer. Otherwise the application will go to that script when the event is triggered and performance will be impacted slightly.
17. Keep use of Applet scripting to a minimum where possible. Attempt to meet business requirements by configuring in Siebel Tools where possible and generally implementing scripts for minor functionality where a given functionality cannot be met using declarative configuration.
18. Scripts which insert new records or change data should take care to explicitly commit the record otherwise the data could be lost.
19. When you are deleting records in script based on a particular query, be sure to use a while loop rather than an 'If' statement as the 'If' condition will only delete one record where multiple records may need to be deleted.
Wrong Way:
1: bcPositionMVG.ClearToQuery();
2: bcPositionMVG.InvokeMethod("SetAdminMode", "TRUE");
3: bcPositionMVG.SetSearchExpr("[Id] <> '0-5220'");
4: bcPositionMVG.ExecuteQuery();
5:
6: // The first record is identified and deleted. However,
7: // subsequent child records are not deleted.
8: if ( bcPositionMVG.FirstRecord() )
9: {
10: bcPositionMVG.DeleteRecord();
11: }
Right Way:
1: bcPositionMVG.ClearToQuery();
2: bcPositionMVG.InvokeMethod("SetAdminMode", "TRUE");
3: bcPositionMVG.SetSearchExpr("[Id] <> '0-5220'");
4: bcPositionMVG.ExecuteQuery();
5:
6: while ( bcPositionMVG.FirstRecord() )
7: {
8: bcPositionMVG.DeleteRecord();
9: }
1. Always use TheApplication to call the application, as the declaration of a global variable to represent the application (e.g. var theApp = TheApplication()) is not recommended by Siebel. The use of this variable may cause memory leaks, reduce performance or other unpredictable behaviour.
2. User-defined functions must be Forward Declared in the general declarations of each script. This avoids compilation errors that may arise if the functions called are not in alphabetical order. The compiler compiles all functions alphabetically and so if one function calls another that is later in the alphabet the compiler does not recognize this second function and therefore, fails.
3. Be cautious when adding script to business components as this code applies application wide across applets and views. If a certain piece of coding is needed at the business component level but is restrictive to certain situations like if exposed only through some particular views then make sure to limit the processing through an appropriate condition.
4. The use of 'With' is recommended by Siebel as it enables the code to be changed faster and more readable way to group operations performed within the same business component. The use of 'With' also presents a slight performance improvement.
5. Using variables can make code maintenance easier due to readability. However overuse of variables increases the amount of operations that have to be performed and can reduce performance slightly.
6. Siebel does not recommend the use of 'Empty'. 'Empty' is an undefined variable which is assigned as type variant. A variant is initially set to a null string (''), which means that any scripts currently using this term will not be affected. However, it is better practice to assign '' rather than 'Empty' to any strings you need to set back to NULL. The use of 'Empty' prevents Option Explicit from checking all other variables are declared correctly.
7. The use of 'ActivateField' prior to a query is the equivalent to the 'SELECT' statement in SQL. The use of 'ActivateField' in Siebel scripts code can be confusing and should be minimized as much as possible as this has a performance impact. However there is nothing worse than receiving a runtime exception: ' was not active...'. When activating fields note that:
a. Siebel system fields (Id, Created, Created By, Last Updated, Last Updated By) are always force active.
b. Fields that have Force Active = Y on the business component are always force active.
c. Fields that have Link Specification = Y on the business component are always force active.
d. Fields that are included in the definition of an applet on the active view if it is bound to a web template item and the 'Show In List' property of the list column or 'Visible' property of the control is TRUE. If the user removes the list column from the 'Columns Displayed' in the list applet, the field may no longer be active after the next query.
e. Fields that are used as part of a calculated field calculation when the calculated field is retrieved for use on the active applet.
8. 'ActivateField' should only be used prior to 'ExecuteQuery' to ensure that a particular field will be activated and included in the equivalent 'SELECT' statement of the query. Therefore 'ActivateField' is usually never to be used with 'this'/'Me' (eg. this.ActivateField('Field1')). This is because you don't usually perform a query in the current context as this would change the on screen query displayed to the user. Siebel actually specifies that the use of ActivateField with 'this' can possibly cause data corruption to occur.
9. When performing a query, always use 'ForwardOnly' after the 'ExecuteQuery' to set the cursor position unless moving back through the returned records. This is a much faster query because it does not create a cache that stores the previous records.
10. If you have a set of 3 or more 'IF Else If' statements then use 'Switch Case' statements instead. This simplifies code and improves performance.
11. It is best practice in Siebel scripting to use the 'Try/Catch/Finally' statements in code. This will ensure that exceptions are caught and handled appropriately and instantiated object variables are always destructed in the finally block (which reduces the chances of memory leak) as the code in the finally block is always executed. Note that object variables should be destroyed in the reverse order they were instantiated.
12. Reduce the number of queries performed as much as possible. Siebel maintains the parent-child relationships defined in links automatically so there is no need to query the child Business Component to obtain records for a given parent. Make use of commands like, 'GetParentBusComp' to access the parent record, instead of re-querying to retrieve record.
13. Don't create objects (BC and BOs) if you need a reference to BC and BO from the current context. Make use of default application variables 'BusComp' and 'BusObject' in this situation.
14. The use of 'ActiveBusObject', 'ActiveBusComp' and 'ActiveApplet' should be limited because the object represented by these statements may change depending on the active applet. Siebel recommends the use of the 'this' object for eScript ('Me' for Siebel VB) wherever possible. 'Me'/'this' represents the object where the code is written, 'ActiveXXX' represents the object behind the current active applet. The use of 'Me'/'this' is a safer method, especially during development when, it is not entirely clear which applet will be active at any given time. It also enables easier interpretation of the scripts because the 'base' object, represented by 'Me'/'this' will never change. The use of 'Me'/'this' also removes the need to store the active BusObject and active BusComp in variables as it does not need to be declared or explicitly destroyed at the end of the function.
15. All code must be indented logically, including comments which efficiently describe what the script is doing. Each new script should include a header comment which provides: Author, Date, Description and Version History for that script.
16. Delete all 'empty' scripts that once contained text. Delete everything, including the function header and footer. Otherwise the application will go to that script when the event is triggered and performance will be impacted slightly.
17. Keep use of Applet scripting to a minimum where possible. Attempt to meet business requirements by configuring in Siebel Tools where possible and generally implementing scripts for minor functionality where a given functionality cannot be met using declarative configuration.
18. Scripts which insert new records or change data should take care to explicitly commit the record otherwise the data could be lost.
19. When you are deleting records in script based on a particular query, be sure to use a while loop rather than an 'If' statement as the 'If' condition will only delete one record where multiple records may need to be deleted.
Wrong Way:
1: bcPositionMVG.ClearToQuery();
2: bcPositionMVG.InvokeMethod("SetAdminMode", "TRUE");
3: bcPositionMVG.SetSearchExpr("[Id] <> '0-5220'");
4: bcPositionMVG.ExecuteQuery();
5:
6: // The first record is identified and deleted. However,
7: // subsequent child records are not deleted.
8: if ( bcPositionMVG.FirstRecord() )
9: {
10: bcPositionMVG.DeleteRecord();
11: }
Right Way:
1: bcPositionMVG.ClearToQuery();
2: bcPositionMVG.InvokeMethod("SetAdminMode", "TRUE");
3: bcPositionMVG.SetSearchExpr("[Id] <> '0-5220'");
4: bcPositionMVG.ExecuteQuery();
5:
6: while ( bcPositionMVG.FirstRecord() )
7: {
8: bcPositionMVG.DeleteRecord();
9: }
Saturday, July 17, 2010
BIP Troubleshooting Steps
Process behind execution of Reports
Purpose: The Reports Business Service enables BI Publisher reports to be executed from the Siebel application via a Workflow Process, or through scripting. The report is generated in the background by connecting to the BI Publisher server. The report output is stored in the Siebel File System and accessed from the My BI Publisher Reports view. The Reports Business Service can not be executed on the Mobile Web Client.
Vanilla Siebel Report Business Service was not configured properly. We had issue in seeing Reports from Siebel UI. This issue is also for Vanilla Reports. When we check in Support Web found an SR which is reconfiguring Report business Services and performed the steps specified in the link below.
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocDsrc=DOCUMENT&bmDocTitle=Siebel%20BI%20Publisher%20Reports%20Business%20Service&viewingMode=1143&bmDocID=823360.1&from=BOOKMARK&bmDocType=BULLETIN))
Troubleshooting Errors While Running Siebel Reports (SBL-OMS-
00203)
To troubleshoot errors while generating Siebel Reports
1. Make sure the XMLP Report Server server component is enabled.
2. Increase the XMLP Report Server server component log level to 5 to create a more detailed log file.
3. Copy the xdodebug.log file to the jre\lib directory.
Additionally, you might encounter an instance where a layout template was registered with one database, but you generated it with a different database, and the generation fails. If this error happens, you must complete the following task.
To regenerate and rerun the report
1. Regenerate the XML data.
2. Reregister the layout template.
3. Regenerate the report.
Troubleshooting Errors while Uploading reports.
The above error may cause for two reasons:
Reason 1: Check for BI Publisher Server with administrator privileges as below
1. Log in to the Oracle BI Publisher Server with administrator privileges
2. Click the Admin tab, and then select Security Configuration (under Security Center).
3. In the Security Model section, check the following
o Model: Siebel Security
o Check the host name and port as the Web Service Endpoint.
o Chesk the Siebel administrator credentials
Reason 2: If the Report Uploaded for second time
Need to delete the report from BI Repository, re-register the report after deleting it from repository and the upload the file.
Resolving Class Not Found Errors
1. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Profile Configuration view.
2. Select the XMLPJvmSubsys profile.
3. For the JVM Classpath profile parameter value in the Profile Parameters subview, Provide a reference to each of the JAR files in the CLASSES directory in the Siebel application root directory (SIEBSRVR_ROOT/CLASSES).
For example, you might enter the following value:
\siebsrvr\CLASSES\bicmn.jar;\siebsrvr\CLASSES\bipres.jar;\siebsrvr\CLASSES\collections.jar;\siebsrvr\CLASSES\fix6312772.jar;\siebsrvr\CLASSES\i18nAPI_v3.jar;\siebsrvr\CLASSES\jdbc12.jar;\siebsrvr\CLASSES\jewt4.jar;\siebsrvr\CLASSES\MQeBase.jar;\siebsrvr\CLASSES\MQeSecurity.jar;\siebsrvr\CLASSES\share.jar;\siebsrvr\CLASSES\Siebel.jar;\siebsrvr\CLASSES\Siebel_JavaDoc.jar;\siebsrvr\CLASSES\SiebelCustomXMLP.jar;\siebsrvr\CLASSES\SiebelJI_enu.jar;\siebsrvr\CLASSES\SiebelSMQ.jar;\siebsrvr\CLASSES\SiebelXMLP.jar;\siebsrvr\CLASSES\versioninfo.jar;\siebsrvr\CLASSES\xdocore.jar;
\siebsrvr\CLASSES\xdoparser.jar;\siebsrvr\CLASSES\xmlparserv2-904.jar;\siebsrvr\CLASSES\XSLFunctions.jar;.
Troubleshooting Errors while applying fix pack.
Make sure that the Siebel repository pointing to single repository.
Process of Optimizing the Generation Performance of Siebel Reports for Large Data Volumes
Note: This task is applicable only to connected mode.
1. Navigate to the Administration - Server Configuration screen, Enterprises, and then Profile Configuration view.
2. In the Profile Configuration view list, select Server Datasource (alias ServerDataSrc).
3. Scroll down to the Profile Parameters, and then click Advanced.
4. In the Profile Parameters list, select Datasource maximum fetch array size (alias DSMaxFetchArraySize), and then change the value to -1.
5. Restart the Siebel Server.
Create Separate Named Datasource For Siebel BI Publisher Reports With Large Data Volumes
1. Create a new Profile (Named Subsystem) by cloning the existing 'Server DataSource' Profile. You would need to use the Copy Record feature to do that.
2. The new profile can be named as 'Reports DataSource' (Alias RptDataSrc).
3. In the 'Profile Parameters' specify all the parameters same as the 'Server Datasource' profile. Make sure you set the Datasource maximum fetch array size 'DSMaxFetchArraySize = -1'.
NOTE: Match up all the parameters (including Hidden and Advanced)
4. Navigate to the Administration - Server Configuration > Enterprises > Component Definitions view. Query for 'XMLP Report Server' component.
5. Click the drop down Menu and select 'Start Reconfiguration'.
6. In the 'Component Parameters’ list applet query for '*Data Source'.
7. Set the value of the following parameters:
a) OM - Data Source = RptDataSrc
b) OM - Named Data Source name = RptDataSrc,GatewayDataSrc
c) Application Datasource = ServerDataSrc
8. Click the drop down menu in the 'Component Definitions' applet and select 'Commit Configuration'.
9. Hit the 'Synchronize' button under the 'Component Definitions'
10. Restart Siebel Server and Gateway Services.
11. Log into the Siebel Application as Siebel Administrator and ensure that the XMLP Report Server component is 'Online'.
12. To ensure that the new parameters are in effect:
- Navigate to Site Map > Administration - Server Configuration > Servers >Components
- In the Component Parameters list applet query for '*Datasource'
- Verify the following parameter values:
a) OM - Data Source = RptDataSrc
b) OM - Named Data Source name = RptDataSrc,GatewayDataSrc
c) Application Datasource = ServerDataSrc
Purpose: The Reports Business Service enables BI Publisher reports to be executed from the Siebel application via a Workflow Process, or through scripting. The report is generated in the background by connecting to the BI Publisher server. The report output is stored in the Siebel File System and accessed from the My BI Publisher Reports view. The Reports Business Service can not be executed on the Mobile Web Client.
Vanilla Siebel Report Business Service was not configured properly. We had issue in seeing Reports from Siebel UI. This issue is also for Vanilla Reports. When we check in Support Web found an SR which is reconfiguring Report business Services and performed the steps specified in the link below.
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocDsrc=DOCUMENT&bmDocTitle=Siebel%20BI%20Publisher%20Reports%20Business%20Service&viewingMode=1143&bmDocID=823360.1&from=BOOKMARK&bmDocType=BULLETIN))
Troubleshooting Errors While Running Siebel Reports (SBL-OMS-
00203)
To troubleshoot errors while generating Siebel Reports
1. Make sure the XMLP Report Server server component is enabled.
2. Increase the XMLP Report Server server component log level to 5 to create a more detailed log file.
3. Copy the xdodebug.log file to the jre\lib directory.
Additionally, you might encounter an instance where a layout template was registered with one database, but you generated it with a different database, and the generation fails. If this error happens, you must complete the following task.
To regenerate and rerun the report
1. Regenerate the XML data.
2. Reregister the layout template.
3. Regenerate the report.
Troubleshooting Errors while Uploading reports.
The above error may cause for two reasons:
Reason 1: Check for BI Publisher Server with administrator privileges as below
1. Log in to the Oracle BI Publisher Server with administrator privileges
2. Click the Admin tab, and then select Security Configuration (under Security Center).
3. In the Security Model section, check the following
o Model: Siebel Security
o Check the host name and port as the Web Service Endpoint.
o Chesk the Siebel administrator credentials
Reason 2: If the Report Uploaded for second time
Need to delete the report from BI Repository, re-register the report after deleting it from repository and the upload the file.
Resolving Class Not Found Errors
1. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Profile Configuration view.
2. Select the XMLPJvmSubsys profile.
3. For the JVM Classpath profile parameter value in the Profile Parameters subview, Provide a reference to each of the JAR files in the CLASSES directory in the Siebel application root directory (SIEBSRVR_ROOT/CLASSES).
For example, you might enter the following value:
\siebsrvr\CLASSES\bicmn.jar;\siebsrvr\CLASSES\bipres.jar;\siebsrvr\CLASSES\collections.jar;\siebsrvr\CLASSES\fix6312772.jar;\siebsrvr\CLASSES\i18nAPI_v3.jar;\siebsrvr\CLASSES\jdbc12.jar;\siebsrvr\CLASSES\jewt4.jar;\siebsrvr\CLASSES\MQeBase.jar;\siebsrvr\CLASSES\MQeSecurity.jar;\siebsrvr\CLASSES\share.jar;\siebsrvr\CLASSES\Siebel.jar;\siebsrvr\CLASSES\Siebel_JavaDoc.jar;\siebsrvr\CLASSES\SiebelCustomXMLP.jar;\siebsrvr\CLASSES\SiebelJI_enu.jar;\siebsrvr\CLASSES\SiebelSMQ.jar;\siebsrvr\CLASSES\SiebelXMLP.jar;\siebsrvr\CLASSES\versioninfo.jar;\siebsrvr\CLASSES\xdocore.jar;
\siebsrvr\CLASSES\xdoparser.jar;\siebsrvr\CLASSES\xmlparserv2-904.jar;\siebsrvr\CLASSES\XSLFunctions.jar;.
Troubleshooting Errors while applying fix pack.
Make sure that the Siebel repository pointing to single repository.
Process of Optimizing the Generation Performance of Siebel Reports for Large Data Volumes
Note: This task is applicable only to connected mode.
1. Navigate to the Administration - Server Configuration screen, Enterprises, and then Profile Configuration view.
2. In the Profile Configuration view list, select Server Datasource (alias ServerDataSrc).
3. Scroll down to the Profile Parameters, and then click Advanced.
4. In the Profile Parameters list, select Datasource maximum fetch array size (alias DSMaxFetchArraySize), and then change the value to -1.
5. Restart the Siebel Server.
Create Separate Named Datasource For Siebel BI Publisher Reports With Large Data Volumes
1. Create a new Profile (Named Subsystem) by cloning the existing 'Server DataSource' Profile. You would need to use the Copy Record feature to do that.
2. The new profile can be named as 'Reports DataSource' (Alias RptDataSrc).
3. In the 'Profile Parameters' specify all the parameters same as the 'Server Datasource' profile. Make sure you set the Datasource maximum fetch array size 'DSMaxFetchArraySize = -1'.
NOTE: Match up all the parameters (including Hidden and Advanced)
4. Navigate to the Administration - Server Configuration > Enterprises > Component Definitions view. Query for 'XMLP Report Server' component.
5. Click the drop down Menu and select 'Start Reconfiguration'.
6. In the 'Component Parameters’ list applet query for '*Data Source'.
7. Set the value of the following parameters:
a) OM - Data Source = RptDataSrc
b) OM - Named Data Source name = RptDataSrc,GatewayDataSrc
c) Application Datasource = ServerDataSrc
8. Click the drop down menu in the 'Component Definitions' applet and select 'Commit Configuration'.
9. Hit the 'Synchronize' button under the 'Component Definitions'
10. Restart Siebel Server and Gateway Services.
11. Log into the Siebel Application as Siebel Administrator and ensure that the XMLP Report Server component is 'Online'.
12. To ensure that the new parameters are in effect:
- Navigate to Site Map > Administration - Server Configuration > Servers >Components
- In the Component Parameters list applet query for '*Datasource'
- Verify the following parameter values:
a) OM - Data Source = RptDataSrc
b) OM - Named Data Source name = RptDataSrc,GatewayDataSrc
c) Application Datasource = ServerDataSrc
BIP Report Installation
BIP Software Download
Installing Oracle Business Intelligence Publisher for
Siebel Business Applications
Installation of BI Publisher Server
1. Log in to Oracle E-Delivery available at:
http://edelivery.oracle.com/EPD/WelcomePage/get_form?ARU_LANG=US
2. Choose a language or select the Continue link to download with English as the default language.
3. Accept the license terms and export restrictions.
4. Select Oracle Business Intelligence as the product pack, a platform (for example, Microsoft Windows (32-bit), and then click Go.
5. Select Oracle Business Intelligence (10.1.3) Media Pack for Microsoft Windows (32-bit), Part
Number B36246-15, and then click Continue(The part number is different if installing a media
pack for other platform).
6. Download the following BI Publisher installations:
Oracle BI Publisher Enterprise 10.1.3.4.0 for Microsoft Windows Part 1 of 2.
Oracle BI Publisher Enterprise 10.1.3.4.0 for Microsoft Windows Part 2 of 2.
7. Install BI Publisher by performing the following tasks
• Unzip the following files into a directory of your choice
B50931-01_1of2.zip
B50931-01_2of2.zip
• Run setup.exe.
Oracle BI Publisher Desktop Installation
Select the language and click next.
Click next.
Click Finish, setup for Oracle BI Publisher Desktop is completed.
Oracle Enterprise Installer
Click next
Enter OC4J Password as Administrator1.
Installation of Oracle BI Publisher is completed.
Login to BI Server as below
Give the UserId and Password as ‘Administrator’.
Note: You must have installed JDK (Java Development Kit) version 1.5 or higher and pointed the JAVA_HOME system variable to the JDK.
Steps to configure BIP Report server
1. Define Outbound Web Service for the BIP Publisher Server
a. Login to Siebel application with SADMIN
b. Navigate Administration - Web Services , Click Outbound Web Service
c. In the Name field, query for ‘PublicReportService’ change Address in Service Ports to http://crmprd02.usac.mmm.com:9704/xmlpserver/services/PublicReportService
2. Copy JAR files to the BI Publisher Server: We need to copy JAR files for successful Report generation. By default, these Java functions are not available on the BI Publisher Server.
a. Copy the following files from $SIEBEL_HOME/CLASSES to OC4J_HOME/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/lib
XSLFunctions.JAR
SiebelCustomXMLP.JAR
SiebelCustomXMLP_SIA.JAR( Applicable only for Industry applications)
b. Enable external file references by performing the following tasks
1) Log in to the BI Publisher Server
2) Click the Admin tab, and then select Runtime Configuration and Properties
3) Change the Default value for the Disable External Reference attribute to FALSE.
c. Restart OC4J( BI Publisher services).
3. Enable Siebel Reports: Before using Siebel Reports, the XMLP Report Server Component must be enabled. By enabling the XMLP Report Server Component, reports appear in the Reports Menu drop-down list in Siebel Business Applications.
To enable Siebel Reports do the following:
a. Log in to the Siebel application with system administrator privileges
b. Navigate to Administration - Server Configuration, Enterprises, and then Component Groups
c. In the Component Groups list, select XMLP Report, and then click Enable.
d. Click the Synchronize view tab, and then in the Component list, select XMLP Report Server
e. Click Synchronize
f. Restart the Siebel Server
4. Configure Database Authentication and Security:
To set the BI Publisher server user ID and password.
a. Log in to your Siebel application.
b. Navigate to Administration - Server Configuration, Servers, and then Components.
c. Query for XMLP Report Server, and then select it.
d. Click the Parameters tab and query for BIP*.
e. Enter the user ID and password used to access the BI Publisher Server in the Default Value fields of the BIP Server Login and BIP Server Password parameters
5. Configure Font Files
On the Siebel Server machine where the XMLP Report Server Component is enabled, copy the fonts you want to use for your reports from, for example, C:\WINDOWS\Fonts directory, to the $JRE_HOME\fonts directory.
Configuration Steps after 8.1.1.1 Fix Pack applied: (Fix Pack to get Parameterized Reports)
Apply 8.1.1.1 Fix Pack Tools, Client and Server (Download the software from Metalink Patches & Updates)
Importing the Siebel CRM 8.1.1.1 Fix Pack SIF File for Use with Siebel Reports
a. Log in to Siebel Tools.
b. From the application-level menu, select Tools, and then the Import from Archive menu item.
c. In the file browser dialog window, choose 8111FP_new_feature.sif from the D:\SIEBEL_TOOLS_ROOT\tools\REPPATCH directory (where Siebel Tools is installed).
d. Follow the import wizard prompts to import the SIF file.
e. Compile the new project into the repository file.
Post installation Configuration Tasks for Oracle BI Publisher
o Configuring the Outbound Web Service for the Oracle BI Publisher Server
1. Generate a new WSDL file by doing the following.
a. Start up the Oracle BI Publisher Server.
b. Using your browser, enter the following URL to retrieve the Web service definition.
http://:/xmlpserver/services/PublicReportService_v11?wsdl
Where:
• host is the full path for your Oracle BI Publisher Server
• port is the port that the Oracle BI Publisher Server uses
c. Save the definition as PublicReportService_v11.WSDL.
2. Using Siebel Tools, delete the PublicReportService outbound Web service and related integrated objects by doing the following.
a. Log in to Siebel Tools.
b. Query for the PublicReportService business service, and then remove this object.
c. Click Integration Object, query for the XMLP Integration project, and then remove all selected objects.
Note: Make sure that tools is pointing single repository.
3. Create the updated PublicReportService by doing the following.
a. In Siebel Tools, choose File, New Objects, the EAI tab, Web Service, and then click OK.
b. Select the XMLP Integration project.
c. Browse to import the PublicReportService_v11.WSDL document file (the file you created in Step 1), and then click Next.
d. Check the Deploy Integration Object(s) and Proxy Business Service(s) checkbox, and then click Finish.
4. Check your results by doing the following.
a. In Siebel Tools, click the Business Service object type.
b. Perform a query with the following criteria:
• Project is XMLP Integration
• Name is PublicReportService
c. Verify the user properties are as follows:
• siebel_port_name is PublicReportService_v11
• siebel_web_service_name is PublicReportServiceService
• siebel_web_service_namespace is
http://xmlns.oracle.com/oxp/service/v11/PublicReportService
5. Select Integration Object, query for the XMLP Integration project, and then verify there 128 projects are returned.
6. Compile the XMLP Integration project.
7. Log in to the Siebel application as an administrator.
8. Navigate to the Administration - Web Services screen, then the Outbound Web Services view.
9. In the Name field, query for PublicReportServiceService, and then change the Oracle BI Publisher Server machine name to your Oracle BI Publisher Server using the following format:
http://:/xmlpserver/services/PublicReportServiceService
Where:
host.domain is the full path for your Oracle BI Publisher Server
port is the port that the Oracle BI Publisher Server uses
For example, you might set it to:
http://.domain:9704/xmlpserver/services/PublicReportServiceService
10. Confirm the new PublicReportServiceService Web service is active by doing the following.
a. Restart the Siebel Server.
b. Navigate to the Administration - Web Services screen, then the Outbound Web Services view.
c. Query for PublicReportServiceService to confirm the status is Active.
d. In the Service Ports subview, verify the Name field shows PublicReportService_v11.
11. Verify that the Oracle BI Publisher Server is running and ready for generating reports.
o To copy JAR files to the Oracle BI Publisher Server ( Ignore these steps if it’s performed before fix pack)
1. Copy the following files from the SIEBSRVR_ROOT/CLASSES directory:
XSLFunctions.JAR
SiebelCustomXMLP.JAR
SiebelCustomXMLP_SIA.JAR
2. Paste them to the following Oracle Application Server directory:
OracleAS_HOME/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/lib
3. Enable the external file references:
a. Log in to the Oracle BI Publisher Server with administrator privileges.
b. Click the Admin tab, and then select Runtime Configuration and Properties.
c. Change the default value for the Disable External Reference attribute to FALSE, click Apply, and then verify the changes were made.
4. Restart Oracle Application Server Containers for Java Platform, Enterprise Edition (OC4J).
o Adding an Explicit Reference to JAR Files for the Oracle BI Publisher Server
1. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Profile Configuration view.
2. Select the XMLPJvmSubsys profile.
3. For the JVM Classpath profile parameter value in the Profile Parameters subview, provide a reference to each of the JAR files in the CLASSES directory in the Siebel application root directory (SIEBSRVR_ROOT/CLASSES).
For example
${SIEBEL_HOME}/classes/SiebelXMLP.jar:${SIEBEL_HOME}/classes/xdoparser.jar:${SIEBEL_HOME}/classes/fix6312772.jar:${SIEBEL_HOME}/classes/xdocore.jar:${SIEBEL_HOME}/classes/xmlparserv2-904.jar:${SIEBEL_HOME}/classes/versioninfo.jar:${SIEBEL_HOME}/classes/share.jar:${SIEBEL_HOME}/classes/jewt4.jar:${SIEBEL_HOME}/classes/jdbc12.jar:${SIEBEL_HOME}/classes/i18nAPI_v3.jar:${SIEBEL_HOME}/classes/collections.jar:${SIEBEL_HOME}/classes/bipres.jar:${SIEBEL_HOME}/classes/bicmn.jar:${SIEBEL_HOME}/classes/Siebel.jar:${SIEBEL_HOME}/classes/XSLFunctions.jar:${SIEBEL_HOME}/classes/SiebelCustomXMLP.jar
Where:
${SIEBEL_HOME} is the actual path where the Siebel application is installed.
4. Restart Siebel services
Process of Configuring Security and Authentication for Siebel Reports
o Setting the Siebel Security Model for Siebel Reports
1. Define four new responsibilities in the Siebel application by doing the following:
a. Navigate to the Administration - Web service screen, then the Inbound Web Service view.
b. Import the BIPSiebelSecurityWS.XML file to create the inbound Web service from the D:\SIEBEL_TOOLS_ROOT\tools\REPPATCH directory (where Siebel Tools is installed).
c. Change the host and port number of the server port's address to that of the Siebel Server.
d. Navigate to the Administration - Application screen, then the Responsibilities view to add the following new responsibilities:
Responsibility Description
XMLP_ADMIN Administrator role for the Oracle BI Publisher Server with no access limitations.
XMLP_DEVELOPER Assign this responsibility to allow for uploading reports from the Oracle BI Publisher Server to the Siebel application.
XMLP_SCHEDULER Assign this responsibility to allow for scheduling of reports.
XMLP_SIEBEL_GUEST Assign this responsibility to limit access to reports. This responsibility only allows for generation, viewing, and deletion of user's own reports.
e. Assign these responsibilities to the appropriate users.
2. Associate the XMLP_SCHEDULER responsibility with the Report Job List View.
This association allows users to view their scheduled reports in the My Jobs view in the Siebel application, which is an embedded user interface to Oracle BI Publisher.
3. Enable the Siebel Security model by doing the following:
a. Log in to the Oracle BI Publisher Server with administrator privileges.
b. Click the Admin tab, then select Security Configuration (under Security Center).
c. Create a super user as shown below and click Apply button.
NOTE: Super user allows you to log into the Oracle BI Publisher Server when the Siebel application is not running.
d. In the Security Model section, perform the following, and then click Apply.
Set the model to Siebel Security
Enter the host name and port as the Web Service Endpoint
Enter the Siebel administrator credentials
4. Set the proper access permissions to the SiebelCRMReports folder by performing the following:
a. Open a new browser window and navigate to the Oracle BI Publisher Server at
http://BIPServerHost:9704/xmlpserver
b. Click the Admin tab, select Roles and Permissions, and then locate the XMLP roles (XMLP_*).
c. For each report responsibility, click Add Folders to grant permission to the shared SiebelCRMReports folder.
5. Restart the Oracle BI Publisher Server.
Installing Oracle Business Intelligence Publisher for
Siebel Business Applications
Installation of BI Publisher Server
1. Log in to Oracle E-Delivery available at:
http://edelivery.oracle.com/EPD/WelcomePage/get_form?ARU_LANG=US
2. Choose a language or select the Continue link to download with English as the default language.
3. Accept the license terms and export restrictions.
4. Select Oracle Business Intelligence as the product pack, a platform (for example, Microsoft Windows (32-bit), and then click Go.
5. Select Oracle Business Intelligence (10.1.3) Media Pack for Microsoft Windows (32-bit), Part
Number B36246-15, and then click Continue(The part number is different if installing a media
pack for other platform).
6. Download the following BI Publisher installations:
Oracle BI Publisher Enterprise 10.1.3.4.0 for Microsoft Windows Part 1 of 2.
Oracle BI Publisher Enterprise 10.1.3.4.0 for Microsoft Windows Part 2 of 2.
7. Install BI Publisher by performing the following tasks
• Unzip the following files into a directory of your choice
B50931-01_1of2.zip
B50931-01_2of2.zip
• Run setup.exe.
Oracle BI Publisher Desktop Installation
Select the language and click next.
Click next.
Click Finish, setup for Oracle BI Publisher Desktop is completed.
Oracle Enterprise Installer
Click next
Enter OC4J Password as Administrator1.
Installation of Oracle BI Publisher is completed.
Login to BI Server as below
Give the UserId and Password as ‘Administrator’.
Note: You must have installed JDK (Java Development Kit) version 1.5 or higher and pointed the JAVA_HOME system variable to the JDK.
Steps to configure BIP Report server
1. Define Outbound Web Service for the BIP Publisher Server
a. Login to Siebel application with SADMIN
b. Navigate Administration - Web Services , Click Outbound Web Service
c. In the Name field, query for ‘PublicReportService’ change Address in Service Ports to http://crmprd02.usac.mmm.com:9704/xmlpserver/services/PublicReportService
2. Copy JAR files to the BI Publisher Server: We need to copy JAR files for successful Report generation. By default, these Java functions are not available on the BI Publisher Server.
a. Copy the following files from $SIEBEL_HOME/CLASSES to OC4J_HOME/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/lib
XSLFunctions.JAR
SiebelCustomXMLP.JAR
SiebelCustomXMLP_SIA.JAR( Applicable only for Industry applications)
b. Enable external file references by performing the following tasks
1) Log in to the BI Publisher Server
2) Click the Admin tab, and then select Runtime Configuration and Properties
3) Change the Default value for the Disable External Reference attribute to FALSE.
c. Restart OC4J( BI Publisher services).
3. Enable Siebel Reports: Before using Siebel Reports, the XMLP Report Server Component must be enabled. By enabling the XMLP Report Server Component, reports appear in the Reports Menu drop-down list in Siebel Business Applications.
To enable Siebel Reports do the following:
a. Log in to the Siebel application with system administrator privileges
b. Navigate to Administration - Server Configuration, Enterprises, and then Component Groups
c. In the Component Groups list, select XMLP Report, and then click Enable.
d. Click the Synchronize view tab, and then in the Component list, select XMLP Report Server
e. Click Synchronize
f. Restart the Siebel Server
4. Configure Database Authentication and Security:
To set the BI Publisher server user ID and password.
a. Log in to your Siebel application.
b. Navigate to Administration - Server Configuration, Servers, and then Components.
c. Query for XMLP Report Server, and then select it.
d. Click the Parameters tab and query for BIP*.
e. Enter the user ID and password used to access the BI Publisher Server in the Default Value fields of the BIP Server Login and BIP Server Password parameters
5. Configure Font Files
On the Siebel Server machine where the XMLP Report Server Component is enabled, copy the fonts you want to use for your reports from, for example, C:\WINDOWS\Fonts directory, to the $JRE_HOME\fonts directory.
Configuration Steps after 8.1.1.1 Fix Pack applied: (Fix Pack to get Parameterized Reports)
Apply 8.1.1.1 Fix Pack Tools, Client and Server (Download the software from Metalink Patches & Updates)
Importing the Siebel CRM 8.1.1.1 Fix Pack SIF File for Use with Siebel Reports
a. Log in to Siebel Tools.
b. From the application-level menu, select Tools, and then the Import from Archive menu item.
c. In the file browser dialog window, choose 8111FP_new_feature.sif from the D:\SIEBEL_TOOLS_ROOT\tools\REPPATCH directory (where Siebel Tools is installed).
d. Follow the import wizard prompts to import the SIF file.
e. Compile the new project into the repository file.
Post installation Configuration Tasks for Oracle BI Publisher
o Configuring the Outbound Web Service for the Oracle BI Publisher Server
1. Generate a new WSDL file by doing the following.
a. Start up the Oracle BI Publisher Server.
b. Using your browser, enter the following URL to retrieve the Web service definition.
http://
Where:
• host is the full path for your Oracle BI Publisher Server
• port is the port that the Oracle BI Publisher Server uses
c. Save the definition as PublicReportService_v11.WSDL.
2. Using Siebel Tools, delete the PublicReportService outbound Web service and related integrated objects by doing the following.
a. Log in to Siebel Tools.
b. Query for the PublicReportService business service, and then remove this object.
c. Click Integration Object, query for the XMLP Integration project, and then remove all selected objects.
Note: Make sure that tools is pointing single repository.
3. Create the updated PublicReportService by doing the following.
a. In Siebel Tools, choose File, New Objects, the EAI tab, Web Service, and then click OK.
b. Select the XMLP Integration project.
c. Browse to import the PublicReportService_v11.WSDL document file (the file you created in Step 1), and then click Next.
d. Check the Deploy Integration Object(s) and Proxy Business Service(s) checkbox, and then click Finish.
4. Check your results by doing the following.
a. In Siebel Tools, click the Business Service object type.
b. Perform a query with the following criteria:
• Project is XMLP Integration
• Name is PublicReportService
c. Verify the user properties are as follows:
• siebel_port_name is PublicReportService_v11
• siebel_web_service_name is PublicReportServiceService
• siebel_web_service_namespace is
http://xmlns.oracle.com/oxp/service/v11/PublicReportService
5. Select Integration Object, query for the XMLP Integration project, and then verify there 128 projects are returned.
6. Compile the XMLP Integration project.
7. Log in to the Siebel application as an administrator.
8. Navigate to the Administration - Web Services screen, then the Outbound Web Services view.
9. In the Name field, query for PublicReportServiceService, and then change the Oracle BI Publisher Server machine name to your Oracle BI Publisher Server using the following format:
http://
Where:
host.domain is the full path for your Oracle BI Publisher Server
port is the port that the Oracle BI Publisher Server uses
For example, you might set it to:
http://
10. Confirm the new PublicReportServiceService Web service is active by doing the following.
a. Restart the Siebel Server.
b. Navigate to the Administration - Web Services screen, then the Outbound Web Services view.
c. Query for PublicReportServiceService to confirm the status is Active.
d. In the Service Ports subview, verify the Name field shows PublicReportService_v11.
11. Verify that the Oracle BI Publisher Server is running and ready for generating reports.
o To copy JAR files to the Oracle BI Publisher Server ( Ignore these steps if it’s performed before fix pack)
1. Copy the following files from the SIEBSRVR_ROOT/CLASSES directory:
XSLFunctions.JAR
SiebelCustomXMLP.JAR
SiebelCustomXMLP_SIA.JAR
2. Paste them to the following Oracle Application Server directory:
OracleAS_HOME/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/lib
3. Enable the external file references:
a. Log in to the Oracle BI Publisher Server with administrator privileges.
b. Click the Admin tab, and then select Runtime Configuration and Properties.
c. Change the default value for the Disable External Reference attribute to FALSE, click Apply, and then verify the changes were made.
4. Restart Oracle Application Server Containers for Java Platform, Enterprise Edition (OC4J).
o Adding an Explicit Reference to JAR Files for the Oracle BI Publisher Server
1. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Profile Configuration view.
2. Select the XMLPJvmSubsys profile.
3. For the JVM Classpath profile parameter value in the Profile Parameters subview, provide a reference to each of the JAR files in the CLASSES directory in the Siebel application root directory (SIEBSRVR_ROOT/CLASSES).
For example
${SIEBEL_HOME}/classes/SiebelXMLP.jar:${SIEBEL_HOME}/classes/xdoparser.jar:${SIEBEL_HOME}/classes/fix6312772.jar:${SIEBEL_HOME}/classes/xdocore.jar:${SIEBEL_HOME}/classes/xmlparserv2-904.jar:${SIEBEL_HOME}/classes/versioninfo.jar:${SIEBEL_HOME}/classes/share.jar:${SIEBEL_HOME}/classes/jewt4.jar:${SIEBEL_HOME}/classes/jdbc12.jar:${SIEBEL_HOME}/classes/i18nAPI_v3.jar:${SIEBEL_HOME}/classes/collections.jar:${SIEBEL_HOME}/classes/bipres.jar:${SIEBEL_HOME}/classes/bicmn.jar:${SIEBEL_HOME}/classes/Siebel.jar:${SIEBEL_HOME}/classes/XSLFunctions.jar:${SIEBEL_HOME}/classes/SiebelCustomXMLP.jar
Where:
${SIEBEL_HOME} is the actual path where the Siebel application is installed.
4. Restart Siebel services
Process of Configuring Security and Authentication for Siebel Reports
o Setting the Siebel Security Model for Siebel Reports
1. Define four new responsibilities in the Siebel application by doing the following:
a. Navigate to the Administration - Web service screen, then the Inbound Web Service view.
b. Import the BIPSiebelSecurityWS.XML file to create the inbound Web service from the D:\SIEBEL_TOOLS_ROOT\tools\REPPATCH directory (where Siebel Tools is installed).
c. Change the host and port number of the server port's address to that of the Siebel Server.
d. Navigate to the Administration - Application screen, then the Responsibilities view to add the following new responsibilities:
Responsibility Description
XMLP_ADMIN Administrator role for the Oracle BI Publisher Server with no access limitations.
XMLP_DEVELOPER Assign this responsibility to allow for uploading reports from the Oracle BI Publisher Server to the Siebel application.
XMLP_SCHEDULER Assign this responsibility to allow for scheduling of reports.
XMLP_SIEBEL_GUEST Assign this responsibility to limit access to reports. This responsibility only allows for generation, viewing, and deletion of user's own reports.
e. Assign these responsibilities to the appropriate users.
2. Associate the XMLP_SCHEDULER responsibility with the Report Job List View.
This association allows users to view their scheduled reports in the My Jobs view in the Siebel application, which is an embedded user interface to Oracle BI Publisher.
3. Enable the Siebel Security model by doing the following:
a. Log in to the Oracle BI Publisher Server with administrator privileges.
b. Click the Admin tab, then select Security Configuration (under Security Center).
c. Create a super user as shown below and click Apply button.
NOTE: Super user allows you to log into the Oracle BI Publisher Server when the Siebel application is not running.
d. In the Security Model section, perform the following, and then click Apply.
Set the model to Siebel Security
Enter the host name and port as the Web Service Endpoint
Enter the Siebel administrator credentials
4. Set the proper access permissions to the SiebelCRMReports folder by performing the following:
a. Open a new browser window and navigate to the Oracle BI Publisher Server at
http://BIPServerHost:9704/xmlpserver
b. Click the Admin tab, select Roles and Permissions, and then locate the XMLP roles (XMLP_*).
c. For each report responsibility, click Add Folders to grant permission to the shared SiebelCRMReports folder.
5. Restart the Oracle BI Publisher Server.
BIP Reports Setup in Siebel
BIP Reports Documentation
Introduction 2
Steps to convert Actuate Report into Oracle BI Publisher 2
Actuate Reports Conversion Assistant 3
Steps to Convert Report Layout 4
Siebel Reporting Architecture with BI Publisher 7
Two Different Modes for BI Publisher Integration 7
Siebel Reports Architecture and Report Flow Generation for Connected Mode 7
Siebel Reports Architecture and Report Flow Generation for Disconnected Mode 9
OBI Publisher Reports 11
1. Create a new Integration Object in Siebel Tools – 11
2. Create sample XML file- 14
3. Create a Report template- 17
4. Register the report template using the Report Template Registration view. 26
5. View Association- 27
Introduction
BI Publisher has been introduced to Siebel users since its Release 8.1.1 as a new reporting platform replacing the older Actuate base reporting platform. It is tightly integrated with the Siebel architecture and its applications. The users can run and manage their reports with BI Publisher from Siebel applications UI.
This document provides detail description of how to convert Actuate reports to BI reports and how to create reports Using OBI Publisher
Steps to convert Actuate Report into Oracle BI Publisher
The Siebel Reports integration with Oracle BI Publisher is based on a loosely coupled architecture where Oracle BI Publisher runs as a standalone server. The integration point for Siebel Reporting will be through standard Web services integration using Siebel EAI. Reports will be submitted and rendered within the context of the Siebel user interface. The reports can be saved within the Siebel file system. Actuate, in a Siebel CRM environment, handles the report layout in an Actuate design File (.ROD file) and the report data comes from Siebel in pre-built report objects (Business Objects, Business Components etc.). In Oracle BI Publisher the data model and the layout are separate entities, therefore, the Actuate Reports Conversion Assistant can assist with part of the reports conversion process.
Actuate Reports Conversion Assistant
Actuate Reports Conversion Assistant is a command line utility that converts the Actuate layout design into BI Publisher layout design. It takes the .BAS file as input that is generated by Actuate Design File (.ROD) during compilation. The conversion tool reads the .BAS file and generates an RTF template for BI Publisher.
Prerequisites
1. Windows OS environment
2. JRE 1.5 or above installed in the machine and this should be set in the Windows path environment variable. To verify the version of java in the machine, type the following in a command prompt:
Java -version
3. If the Java version is lower than 1.5 then you must change the path at the command prompt to the higher version:
Set path = [enter the path to a higher version of Java.exe]; %path%
Note: The complete install of Oracle BI Publisher 10.1.3.4 includes a JDK 1.5 installation.
Steps to Convert Report Layout
1. Extract the files from ActuateConversionAssistant_v1.00.zip to a suitable location
2. From a Windows command prompt navigate to the extracted locations and the ‘scripts’ folder.
3. Type "run" to start the conversion. The run command can have the following options:
run –i -o
Introduction 2
Steps to convert Actuate Report into Oracle BI Publisher 2
Actuate Reports Conversion Assistant 3
Steps to Convert Report Layout 4
Siebel Reporting Architecture with BI Publisher 7
Two Different Modes for BI Publisher Integration 7
Siebel Reports Architecture and Report Flow Generation for Connected Mode 7
Siebel Reports Architecture and Report Flow Generation for Disconnected Mode 9
OBI Publisher Reports 11
1. Create a new Integration Object in Siebel Tools – 11
2. Create sample XML file- 14
3. Create a Report template- 17
4. Register the report template using the Report Template Registration view. 26
5. View Association- 27
Introduction
BI Publisher has been introduced to Siebel users since its Release 8.1.1 as a new reporting platform replacing the older Actuate base reporting platform. It is tightly integrated with the Siebel architecture and its applications. The users can run and manage their reports with BI Publisher from Siebel applications UI.
This document provides detail description of how to convert Actuate reports to BI reports and how to create reports Using OBI Publisher
Steps to convert Actuate Report into Oracle BI Publisher
The Siebel Reports integration with Oracle BI Publisher is based on a loosely coupled architecture where Oracle BI Publisher runs as a standalone server. The integration point for Siebel Reporting will be through standard Web services integration using Siebel EAI. Reports will be submitted and rendered within the context of the Siebel user interface. The reports can be saved within the Siebel file system. Actuate, in a Siebel CRM environment, handles the report layout in an Actuate design File (.ROD file) and the report data comes from Siebel in pre-built report objects (Business Objects, Business Components etc.). In Oracle BI Publisher the data model and the layout are separate entities, therefore, the Actuate Reports Conversion Assistant can assist with part of the reports conversion process.
Actuate Reports Conversion Assistant
Actuate Reports Conversion Assistant is a command line utility that converts the Actuate layout design into BI Publisher layout design. It takes the .BAS file as input that is generated by Actuate Design File (.ROD) during compilation. The conversion tool reads the .BAS file and generates an RTF template for BI Publisher.
Prerequisites
1. Windows OS environment
2. JRE 1.5 or above installed in the machine and this should be set in the Windows path environment variable. To verify the version of java in the machine, type the following in a command prompt:
Java -version
3. If the Java version is lower than 1.5 then you must change the path at the command prompt to the higher version:
Set path = [enter the path to a higher version of Java.exe]; %path%
Note: The complete install of Oracle BI Publisher 10.1.3.4 includes a JDK 1.5 installation.
Steps to Convert Report Layout
1. Extract the files from ActuateConversionAssistant_v1.00.zip to a suitable location
2. From a Windows command prompt navigate to the extracted locations and the ‘scripts’ folder.
3. Type "run" to start the conversion. The run command can have the following options:
run –i
Siebel Upgrade from 7.8 to 8.1
1 In-Scope
• Setup of the Development Environment
• Changes to the User Interface, Scripts, and Data Models
• Validation of Workflows, which include Business Services
• Impact Analysis for all interfaces after the upgrade to Siebel 8.1.1. Only the Impact Analysis - Interfaces report will be prepared
• Unit Testing of the User Interface. This will include script validation
• Tracking and resolution of defects and issues
• Functionality testing for 500 test cases for the web client. Only existing test cases will be used
• Install OBI server and configure to Siebel 8.1.1 development upgrade environment
• Analysis of the vanilla Siebel 8.1.1 reports. Configure those that closely matches the existing Siebel 7.8 vanilla reports
• Configure all reports with minimal configuration in terms of additional labels changes and fields
• Prepare a report for all the customized/Complex reports that can not be configured before end of this project
2.2 Out of Scope
• End to end testing of all interfaces
• Development of any Interfaces integrated with Siebel 7.8 after upgrade to Siebel 8.1
• Setup and validation of interfaces (if required) for successful execution of test cases
• Development of the Customized/Complex BI reports which can not be configured before end of the project
• Test environment setup, system integration testing and UAT
• Remote user testing
• Performance testing
• Setup of the Development Environment
• Changes to the User Interface, Scripts, and Data Models
• Validation of Workflows, which include Business Services
• Impact Analysis for all interfaces after the upgrade to Siebel 8.1.1. Only the Impact Analysis - Interfaces report will be prepared
• Unit Testing of the User Interface. This will include script validation
• Tracking and resolution of defects and issues
• Functionality testing for 500 test cases for the web client. Only existing test cases will be used
• Install OBI server and configure to Siebel 8.1.1 development upgrade environment
• Analysis of the vanilla Siebel 8.1.1 reports. Configure those that closely matches the existing Siebel 7.8 vanilla reports
• Configure all reports with minimal configuration in terms of additional labels changes and fields
• Prepare a report for all the customized/Complex reports that can not be configured before end of this project
2.2 Out of Scope
• End to end testing of all interfaces
• Development of any Interfaces integrated with Siebel 7.8 after upgrade to Siebel 8.1
• Setup and validation of interfaces (if required) for successful execution of test cases
• Development of the Customized/Complex BI reports which can not be configured before end of the project
• Test environment setup, system integration testing and UAT
• Remote user testing
• Performance testing
Interface Impact Analysis Report of Siebel 8.1.1
1.OVERVIEW:
To identify the impact of this upgrade on the existing Siebel7.8 interfaces, detailed impact analysis is performed. This document covers the interface impacts identified and discuss the proposed solutions.
2.SCOPE:
Analyzed the existing Interfaces in Siebel 7.8 Application to identify
1.Architectural and supported platforms impact on Interfaces
2.Upgrade impact on Siebel interface objects(IOs, Workflows, Scripts..etc)
3.External Application Impact
3.REFERENCE DOCUMENTS AND ARTIFACTS:
•http://w76162.usac.mmm.com/CRMA/index.html
•System Requirement Specifications guide of 7.8, 8.1
•Siebel 7.8 application and Tools Repository
4.ARCHITECTURAL IMPACTS:
All real time interfaces in Siebel 7.8 application are using IBM MQSeries Application Messaging Interface1.2.4 (AMI) transport
Oracle stopped supporting AMI transport starting Siebel7.8 onwards. Some customers got it working on 7.8 as the transport business service was still available at the repository but they did so at their own risk.
There was no formal support for AMI at 7.8 and the transport has not been maintained or enhanced since 7.7
Hence, we will not be able to continue with AMI transport in Siebel 8.1 application.
Supporting Documentation:
https://support.oracle.com/CSP/ui/flash.html#tab=Dashboard(page=Dashboard&id=g2ta6nki()),(page=SRView&id=g2tbb3om(sr_stmt=Does%20the%20EAI%20MQSeries%20AMI%20Transport%20work%20in%208.1.1%20and%20if%20yes,%20will%20it%20gets%20su...&&sr_number=3-1167762381&sr_row_id=3-JB977X))
https://metalink3.oracle.com/od/faces/secure/km/DocumentDisplay.jspx?id=477793.1
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=498587.1
4.1 Available Solutions:
The below are the 3 supported Interfaces as alternatives for latest version of Siebel application.
1. EAI JMS Transport
2. EAI MQ Series Server Transport
3. Other Transports
EAI JMS Transport
MQ can be configured to act as a JMS server and siebel can access a remote MQ+JMS server. However, all applications exchanging messages with siebel need to use JMS methods to put or read messages to the MQ queue. The reason is a "pure" MQ message lacks headers and other information a JMS message has. As a result, a message put by a 3rd party application into an MQ queue NOT using JMS methods would NOT be readable by Siebel.
The reverse is also true. A JMS message put at an MQ queue by Siebel using JMS methods would not be readable by applications not using JMS methods to read it.
It means you have to re-design the 3rd party applications to use JMS too.
EAI MQ Series Server Transport
If EAI MQ Series Server Transport is used siebel server that interacts with MQ , a whole MQ server needs to be installed at the same machine.
Unlike AMI, you can not access a remote MQ queue with this transport.
The MQ server has to be at the same box as the siebel server.
This may have an impact on MQ licenses as you may have to license multiple MQ servers.
Other Transports
EAI allows other transports such as EAI HTTP Transport, EAI File Transport, and even custom transports (custom business services you code yourself) but they are not standard QUEUE transports. They do not provide the same guarantees and features as a queue transport.
4.3 Impact to Siebel:
• Software Installation
Software’s to be installed on Windows Servers where Workflow Process Manager Siebel Server component operates.
1. IBM Websphere MQ Client Version 6.0.2.2
2. Java Virtual Machine
Download ms0n.zip, ms0B.zip, me01.zip from IBM support site. Extract the files to JMS\GUITool
•Setting up the JVM Receiver Component Parameter & Subsystem
Need to setup JMS Receiver Component Parameters in Enterprise Servers – Component Definitions
Setting up the JVM Subsystem Types
Need to specify the required parameters like JVM Subsystem name
ReceiveQueue name
Impact to MW & Other applications:
1. Middleware Queue Type needs to be modified in accordance with JMS Transport
2. Chances of discrepancy of JMS Headers with the Middleware and External Applications
3. If JMS transport communication port is not open, enable the ports
4. Middleware team has to investigate for further Impact while migrating from AMI Transport to JMS Transport
Configuration Impacts:
1. Need to make use of EAI JMS Transport instead of EAI MQSeries AMI Transport
2. Slight modification with the default branches in the workflows
3. Some of the Upgrade workflow issues needs to addressed
4. Integration Object Issues
5. Unit test all the interfaces and fix the issues
Out of Scope
• End to end testing of Interfaces in 7.8
• Testing of Interfaces that does not have sufficient details and XML files
• Development of any Interfaces integrated with Siebel 7.8 after upgrade to Siebel 8.1
• Setup and validation of interfaces (if required) for successful execution of test cases
To identify the impact of this upgrade on the existing Siebel7.8 interfaces, detailed impact analysis is performed. This document covers the interface impacts identified and discuss the proposed solutions.
2.SCOPE:
Analyzed the existing Interfaces in Siebel 7.8 Application to identify
1.Architectural and supported platforms impact on Interfaces
2.Upgrade impact on Siebel interface objects(IOs, Workflows, Scripts..etc)
3.External Application Impact
3.REFERENCE DOCUMENTS AND ARTIFACTS:
•http://w76162.usac.mmm.com/CRMA/index.html
•System Requirement Specifications guide of 7.8, 8.1
•Siebel 7.8 application and Tools Repository
4.ARCHITECTURAL IMPACTS:
All real time interfaces in Siebel 7.8 application are using IBM MQSeries Application Messaging Interface1.2.4 (AMI) transport
Oracle stopped supporting AMI transport starting Siebel7.8 onwards. Some customers got it working on 7.8 as the transport business service was still available at the repository but they did so at their own risk.
There was no formal support for AMI at 7.8 and the transport has not been maintained or enhanced since 7.7
Hence, we will not be able to continue with AMI transport in Siebel 8.1 application.
Supporting Documentation:
https://support.oracle.com/CSP/ui/flash.html#tab=Dashboard(page=Dashboard&id=g2ta6nki()),(page=SRView&id=g2tbb3om(sr_stmt=Does%20the%20EAI%20MQSeries%20AMI%20Transport%20work%20in%208.1.1%20and%20if%20yes,%20will%20it%20gets%20su...&&sr_number=3-1167762381&sr_row_id=3-JB977X))
https://metalink3.oracle.com/od/faces/secure/km/DocumentDisplay.jspx?id=477793.1
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=498587.1
4.1 Available Solutions:
The below are the 3 supported Interfaces as alternatives for latest version of Siebel application.
1. EAI JMS Transport
2. EAI MQ Series Server Transport
3. Other Transports
EAI JMS Transport
MQ can be configured to act as a JMS server and siebel can access a remote MQ+JMS server. However, all applications exchanging messages with siebel need to use JMS methods to put or read messages to the MQ queue. The reason is a "pure" MQ message lacks headers and other information a JMS message has. As a result, a message put by a 3rd party application into an MQ queue NOT using JMS methods would NOT be readable by Siebel.
The reverse is also true. A JMS message put at an MQ queue by Siebel using JMS methods would not be readable by applications not using JMS methods to read it.
It means you have to re-design the 3rd party applications to use JMS too.
EAI MQ Series Server Transport
If EAI MQ Series Server Transport is used siebel server that interacts with MQ , a whole MQ server needs to be installed at the same machine.
Unlike AMI, you can not access a remote MQ queue with this transport.
The MQ server has to be at the same box as the siebel server.
This may have an impact on MQ licenses as you may have to license multiple MQ servers.
Other Transports
EAI allows other transports such as EAI HTTP Transport, EAI File Transport, and even custom transports (custom business services you code yourself) but they are not standard QUEUE transports. They do not provide the same guarantees and features as a queue transport.
4.3 Impact to Siebel:
• Software Installation
Software’s to be installed on Windows Servers where Workflow Process Manager Siebel Server component operates.
1. IBM Websphere MQ Client Version 6.0.2.2
2. Java Virtual Machine
Download ms0n.zip, ms0B.zip, me01.zip from IBM support site. Extract the files to JMS\GUITool
•Setting up the JVM Receiver Component Parameter & Subsystem
Need to setup JMS Receiver Component Parameters in Enterprise Servers – Component Definitions
Setting up the JVM Subsystem Types
Need to specify the required parameters like JVM Subsystem name
ReceiveQueue name
Impact to MW & Other applications:
1. Middleware Queue Type needs to be modified in accordance with JMS Transport
2. Chances of discrepancy of JMS Headers with the Middleware and External Applications
3. If JMS transport communication port is not open, enable the ports
4. Middleware team has to investigate for further Impact while migrating from AMI Transport to JMS Transport
Configuration Impacts:
1. Need to make use of EAI JMS Transport instead of EAI MQSeries AMI Transport
2. Slight modification with the default branches in the workflows
3. Some of the Upgrade workflow issues needs to addressed
4. Integration Object Issues
5. Unit test all the interfaces and fix the issues
Out of Scope
• End to end testing of Interfaces in 7.8
• Testing of Interfaces that does not have sufficient details and XML files
• Development of any Interfaces integrated with Siebel 7.8 after upgrade to Siebel 8.1
• Setup and validation of interfaces (if required) for successful execution of test cases
JMS Transport
JMS Setup
1) Downloaded ms0n.zip, ms0B.zip, me01.zip and ms0n.tar from IBM support site.
2) Extracted the zip files to the location F:\JMS\GUITool
com.ibm.mq.pcf-6.1.jar
jmsadmingui.jar
mqcontext.jar
jmsadmingui.bat
Note: The above mentioned files were created in this folder.
3) Created jndi.properties.txt in F:\JMS\JNDI
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory java.naming.provider.url=file:/ F:\JMS\JNDI
4) Set the correct path settings in jmsadmingui.bat file
Go to F:\JMS\GUITool and edit the jmsadmingui.bat file and set the
• current directory (CUR)
• MQJ
• PATH
• CLASSPATH.
Note: In the CLASSPATH specify all the jar files that were extracted from zip files and jar files located in the C:\PrograFiles\IBM\WebSphere MQ\Java\lib.
5) Modified the JMSAdmin.config file
Navigate to C:\Program Files\ibm\WebSphere MQ\Java\bin under MQSeries installation. Edit JMSAdmin.config file and perform the following modifications
• INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
• PROVIDER_URL=file:/F:\JMS\GUITool
Details to be filled by the Middleware team:
Step 1: Run (jmsadmingui.bat) Batch File
Go to F:\JMS\GUITool\ jmsadmingui.bat
Step 2: Select the JMSAdmin.config file in the GUI Tool.
C:\Program Files\IBM\WebSphere MQ\Java\bin\ JMSAdmin.config
Sept 3: Specify the file path
file:/F:\JMS\GUITool
Example Queue Creation
Example ConnectionFactory Creation
Save it and make sure .bindings files gets created under F:\JMS\GUITool
JVM Subsystem Setup
The following steps can be used to create the JVM subsystem using the Siebel WebClient
1. Start any Siebel Business Application and navigate to Site Map → Administration → Server Configuration → Enterprises.
2. In the top list applet, select the Enterprise Server that you want to configure.
3. In the middle applet, click the Profile Configuration tab.
4. Click New to create a new component profile and set the following parameters:
Profile = JAVA
Alias = JAVA
Subsystem Type = JVMSubsys
5. In the Profile Parameters list applet (the bottom applet), set the following values:
a) Set the Value of the JVM Classpath parameter to contain the following:
• The location of the JNDI.properties
• The JMS provider JAR files.
• The Siebel.jar and SiebelJI_lang.jar files.
E:\seaNAM811DEV\siebsrvr\CLASSES\ SiebelJI_enu.jar
E:\seaNAM811DEV\siebsrvr\CLASSES\ Siebel.jar
b) Set the Value of the JVM DLL Name parameter to the path where you have the jvm.dll file installed. For example,
C:\Program Files\Java\j2re1.4.2_16\bin\client \jvm.dll
c) Set the Value of the JVM Options record to any JVM-specific options that you would like to enable. For example,
-Xrs -Djava.compiler=NONE
JMS Sub System Setup:
The following procedure can be used for creating the JMS Transport subsystem using the Siebel Web Client.
1. Start any Siebel Business Application and navigate to Administration → Server Configuration → Enterprises.
2. In the top list applet, select the desired Enterprise Server that you want to configure.
3. In the middle applet, click the Profile Configuration tab.
4. Click New to create a new component profile and set the following parameters:
Profile = M3-HISD-SOFTRAX
Alias = M3-HISD-SOFTRAX
Subsystem Type = JMSSubsys
5. In the Profile Parameters list applet (the bottom applet), specify the following parameters
• ConnectionFactory name =com.ibm.mq.jms.MQQueueConnectionFactory
• JVM Subsystem name = JAVA
• ReceiveQueue name =
• Receive Timeout = 20000
Data Handling Sub system Setup:
To create a JMS Receiver subsystem using the Siebel Web Client a user should follow the steps below:
1. Start any Siebel Business Application and navigate to Administration → Server Configuration → Enterprises.
2. In the top list applet, select the desired Enterprise Server.
3. In the middle applet, click the Profile Configuration tab.
4. Click New to create a new component profile and set the following parameters:
Profile = M3-HISD-SOFTRAX-DHSS
Alias = M3-HISD-SOFTRAX-DH
Subsystem Type = EAITransportDataHandlingSubsys
5. In the Profile Parameters list applet (the bottom applet), specify the following parameters
Workflow Process to Execute = M3 HISD-Softrax RECV WF
Listener Component Setup:
1. Start any Siebel Business Application and navigate to Administration → Server Configuration → Enterprises.
2. In the top list applet, select the desired Enterprise Server.
Component = M3 HISD-Softrax Integration
Component Type = Enterprise Application Integration Receiver
3. Component Parameters Applet
Receiver Service Name = EAI JMS Transport
EAI JMS Transport = ReceiveDispatch
Receiver Connection Subsystem = M3-HISD-SOFTRAX
Receiver Data Handling Subsyst = M3-HISD-SOFTRAX-DH
1) Downloaded ms0n.zip, ms0B.zip, me01.zip and ms0n.tar from IBM support site.
2) Extracted the zip files to the location F:\JMS\GUITool
com.ibm.mq.pcf-6.1.jar
jmsadmingui.jar
mqcontext.jar
jmsadmingui.bat
Note: The above mentioned files were created in this folder.
3) Created jndi.properties.txt in F:\JMS\JNDI
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory java.naming.provider.url=file:/ F:\JMS\JNDI
4) Set the correct path settings in jmsadmingui.bat file
Go to F:\JMS\GUITool and edit the jmsadmingui.bat file and set the
• current directory (CUR)
• MQJ
• PATH
• CLASSPATH.
Note: In the CLASSPATH specify all the jar files that were extracted from zip files and jar files located in the C:\PrograFiles\IBM\WebSphere MQ\Java\lib.
5) Modified the JMSAdmin.config file
Navigate to C:\Program Files\ibm\WebSphere MQ\Java\bin under MQSeries installation. Edit JMSAdmin.config file and perform the following modifications
• INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
• PROVIDER_URL=file:/F:\JMS\GUITool
Details to be filled by the Middleware team:
Step 1: Run (jmsadmingui.bat) Batch File
Go to F:\JMS\GUITool\ jmsadmingui.bat
Step 2: Select the JMSAdmin.config file in the GUI Tool.
C:\Program Files\IBM\WebSphere MQ\Java\bin\ JMSAdmin.config
Sept 3: Specify the file path
file:/F:\JMS\GUITool
Example Queue Creation
Example ConnectionFactory Creation
Save it and make sure .bindings files gets created under F:\JMS\GUITool
JVM Subsystem Setup
The following steps can be used to create the JVM subsystem using the Siebel WebClient
1. Start any Siebel Business Application and navigate to Site Map → Administration → Server Configuration → Enterprises.
2. In the top list applet, select the Enterprise Server that you want to configure.
3. In the middle applet, click the Profile Configuration tab.
4. Click New to create a new component profile and set the following parameters:
Profile = JAVA
Alias = JAVA
Subsystem Type = JVMSubsys
5. In the Profile Parameters list applet (the bottom applet), set the following values:
a) Set the Value of the JVM Classpath parameter to contain the following:
• The location of the JNDI.properties
• The JMS provider JAR files.
• The Siebel.jar and SiebelJI_lang.jar files.
E:\seaNAM811DEV\siebsrvr\CLASSES\ SiebelJI_enu.jar
E:\seaNAM811DEV\siebsrvr\CLASSES\ Siebel.jar
b) Set the Value of the JVM DLL Name parameter to the path where you have the jvm.dll file installed. For example,
C:\Program Files\Java\j2re1.4.2_16\bin\client \jvm.dll
c) Set the Value of the JVM Options record to any JVM-specific options that you would like to enable. For example,
-Xrs -Djava.compiler=NONE
JMS Sub System Setup:
The following procedure can be used for creating the JMS Transport subsystem using the Siebel Web Client.
1. Start any Siebel Business Application and navigate to Administration → Server Configuration → Enterprises.
2. In the top list applet, select the desired Enterprise Server that you want to configure.
3. In the middle applet, click the Profile Configuration tab.
4. Click New to create a new component profile and set the following parameters:
Profile = M3-HISD-SOFTRAX
Alias = M3-HISD-SOFTRAX
Subsystem Type = JMSSubsys
5. In the Profile Parameters list applet (the bottom applet), specify the following parameters
• ConnectionFactory name =com.ibm.mq.jms.MQQueueConnectionFactory
• JVM Subsystem name = JAVA
• ReceiveQueue name =
• Receive Timeout = 20000
Data Handling Sub system Setup:
To create a JMS Receiver subsystem using the Siebel Web Client a user should follow the steps below:
1. Start any Siebel Business Application and navigate to Administration → Server Configuration → Enterprises.
2. In the top list applet, select the desired Enterprise Server.
3. In the middle applet, click the Profile Configuration tab.
4. Click New to create a new component profile and set the following parameters:
Profile = M3-HISD-SOFTRAX-DHSS
Alias = M3-HISD-SOFTRAX-DH
Subsystem Type = EAITransportDataHandlingSubsys
5. In the Profile Parameters list applet (the bottom applet), specify the following parameters
Workflow Process to Execute = M3 HISD-Softrax RECV WF
Listener Component Setup:
1. Start any Siebel Business Application and navigate to Administration → Server Configuration → Enterprises.
2. In the top list applet, select the desired Enterprise Server.
Component = M3 HISD-Softrax Integration
Component Type = Enterprise Application Integration Receiver
3. Component Parameters Applet
Receiver Service Name = EAI JMS Transport
EAI JMS Transport = ReceiveDispatch
Receiver Connection Subsystem = M3-HISD-SOFTRAX
Receiver Data Handling Subsyst = M3-HISD-SOFTRAX-DH
'Sneha Geetam' Review: Youthful, Lively And Contemporary
 | |
 | |
|
స్నేహగీతం-4/5-A must watch
స్నేహగీతం-4/5-A must watch
శిద్దారెడ్డి వెంకట్ | Jul 16, 2010 | 25 comments
ఎప్పుడో రెండేళ్ళ క్రితం అనౌన్స్ అయ్యి అప్పటినుంచీ అప్పుడూ ఇప్పుడూ అంటూ అసలు విడుదలవుతుందో లేదో అనే అనుమానం వచ్చేలా డేట్ మీద డేట్ postpone చేసుకుంటూ మొత్తానికి ఈ రోజు విడుదలవుతున్న స్నేహగీతం సినిమా గురించి వివరంగా చెప్పాలన్నా పూర్తిగా విశ్లేశించాలన్నా ఇంకా కొంత సమయం కావాలి. ప్రస్తుతానికయితే స్నేహగీతం ట్రాన్స్ లో రాస్తున్న ఒక పరిచయం లేదా రికమెండేషన్ అనుకోవచ్చు.
ఒక్క మాటలో చెప్పేయ్యాలంటే స్నేహగీతం is worth your money and time. Go and watch it.
సాధారణంగా బాగా చదువుకుని ప్రపంచం చూసి సినిమా అంటే ప్యాశన్ తో ఈ మధ్యకాలంలో వచ్చిన ఎంతో మంది యువదర్శకులు తమ మొదటి సినిమాగా ఒక యువతీయువకుల బృందం చుట్టూ కాలేజి నేపథ్యంలో తిరిగే కథలను (Thanks to happy days) ఎన్నుకోవడం మనం చూస్తూనే ఉన్నాం. హ్యపీడేస్ తర్వాత ఇలాంటి సినిమాలు వచ్చాయి. ఇక ముందు కూడా ఇలాంటివి రావొచ్చు. స్నేహగీతం కూడా ఈ వెల్లువలో వచ్చి కొట్టుకుపోయే సినిమా ఏమో అనుకున్నా కానీ అలా అనుకునే వారి అభిప్రాయం తప్పని నిరూపించారు శ్రీధర్స్ ఆఫ్ స్నేహగీతం.
కథగా చెప్పాల్సి వస్తే స్నేహగీతం ఆరుగురు మిత్రుల కథ. మొదట కాలేజిలో ఆ తర్వాత కాలేజ్ బయట వారి జీవితాలు, వారిaspirations, dreams, goals, మధ్యలో కాస్త ప్రేమ, కాస్త fun, మధ్యలో కొన్ని కష్టాలు చివరికి సుఖాంతమైన జీవితాలు. ఇంకా చెప్పాలంటే It’s a realistic journey through the lives of realistic characters who talk and behave like us.
ఈ సినిమా గురించి చెప్పుకోవాల్సిన విషయాలు చాలానే ఉన్నాయి. కానీ ఆ విషయాలన్నీ చెప్పేస్తే సినిమాలోని ఆసక్తికరమైన అంశాలను రివీల్ చెయ్యాల్సి వస్తుంది కాబట్టి ఆ పని ఇంకొన్ని రోజులకి వాయిదా వేస్తున్నాను. ప్రస్తుతానికి ఆ సినిమా గురించి మాట్లాడాలంటే superlatives ద్వారానే చెప్పగలను.
ముందుగా స్నేహగీతం అనే సినిమా ద్వారా “The Sridhars (లగడపాటి మరియు మధుర) have pulled of a rare feat” అని చెప్పొచ్చు. ఎందుకంటున్నానంటే ఈ సినిమా దాదాపు అందరూ కొత్తవాళ్ళతో తీసినా ఎక్కడా యాక్టింగ్ లో ఆర్టిఫిషియాలిటీ కనిపించదు. ఆ విధంగా casting పరంగా ఇదొక rare feat అని చెప్పొచ్చు. ప్రతీ సినిమాలోనూ చూసిన మొహాలే చూసి బోర్ కొట్టేసిన తరుణంలో ఎంతో ఈజ్ తో కొత్తవాళ్ళతో performance రాబట్టుకోవడం ఒక అద్భుతమనే చెప్పాలి.
Snehageetham is also a film that speaks to the new generation. ఇంతవరకూ ఎన్ని యూత్ ఫిలింస్ వచ్చినా స్నేహగీతంలోలా ఒక generation యొక్క డ్రీమ్స్, aspirations, confusion లాంటి అంశాలను సరిగ్గా డీల్ చేసిన సినిమా ఒక్కటీ రాలేదు. ఇందులో నటించిన నటీ నటులు మన మధ్యలో ఒకరిగా అనిపిస్తారు. అందంగా ప్లాస్టిక్ స్మైల్స్ ఉన్న అమ్మాయిలు అసలే లేరు. ఉన్న ముగ్గురమ్మాయిలూ ఎంతో న్యాచురల్ గా ఉన్నారు. కొంచెం కామిక్ టచ్ ఉన్న పాత్రలో నటించిన సౌమ్య కూడా మనం రోజూ చూసే అమ్మాయిలానే ఉంటుంది, అలాగే అబ్బాయిలు కూడా…వారిలో ఒక rawness కనిపిస్తుంది. This really added to the realistic feel of the film.
Snehageetham is a film with all the emotions blended very smoothly and it definitely caters to all the classes of audience. సినిమా మొత్తం ఎంతో lighter vein లో నడుస్తుంది. అయినా కూడా సరైన సమయంలో సరైన చోట emotions ఒక పీక్ కి చేరుకునేలా చేసి సినిమా అద్యంతం ప్రేక్షకులకు బోర్ కొట్టకుండా చేయడంలో దర్శకుడు సఫలమయ్యాడు. ముఖ్యంగా ద్వీతియార్థంలో pace చాలా బావుంది.
Snehageetham makes you laugh and at times it also makes you cry. All in all it entertains and at times enlightens you.
ఇంకా చెప్పాలంటే
1) దర్శకుడు కథను ఎక్కడా డైవర్ట్ చెయ్యకుండా to the point ఉండేలా care తీసుకున్న తీరు
2) సినిమాలో ముఖ్ భూమికలు పోషించిన ఐదు మంది కథలనూ ఎంతో బాగా బ్యాలెన్స్ చేసుకుంటూ వచ్చిన విధానం
3) ఈ సినిమా సందేశాత్మక చిత్రం అని అనిపించినా ఎక్కడా పెద్దగా preachy గా అనిపించకపోవడం
4) సంగీతం
5) ఎడిటింగ్
లాంటి ఎన్నో అంశాల కారణంగా ఈ సినిమాని నేనైతే Must Watch సినిమాగా రికమెండ్ చేస్తున్నాను.
స్నేహగీతం లాంటి సినిమాని చూసి ఆదరించండి.తెలిసిన స్టార్స్ లేరనో, చిన్న సినిమా అనో, పైరేటెడ్ డివిడి వస్తే చూద్దామనో, ఆన్ లైన్లో వస్తుందనో ఇంకా పోతే టివిలో వస్తుంది కదా అనో ఈ సినిమా ని థియేటర్లలో చూడడానికి ప్రేక్షకులు రాకపోతే మంచి తెలుగు సినిమాలు అసలు రాకుండా పోతాయి. మంచి సినిమాని ఆదరించండి. స్నేహగీతం చూడండి. మీ ఇంటిల్లపాదీ హాయిగా చూడదగ్గ సినిమా….మీరూ చూడండి మరింత మందికి చూపించండి. ముఖ్యంగా సినిమాలో లీడ్ రోల్స్ లో నటించిన యువతీ యువకులు కాకుండా క్యారెక్టర్ ఆర్టిస్టులు ఎంతో మంది కొత్త వారిని ఈ సినిమాలో పరిచయం చేశారు. వేణు మాధవ్, వెన్నెల కిషోర్ లాంటి ఒకరిద్దరు తప్పితే సినిమా మొత్తం కొత్త వాళ్ళే….మీరీ సినిమాని థియేటర్లలో చూసి విజయవంతం చేసి వారందరికీ మీ ఆదరాభిమానాలు అందచేయాలని కోరుకుంటూ శెలవు తీసుకుంటున్నాను.
Subscribe to:
Posts (Atom)