Showing posts with label SCREATIONS9 - ORACLE shiva shankar reddy likki sharepoint cognos. Show all posts
Showing posts with label SCREATIONS9 - ORACLE shiva shankar reddy likki sharepoint cognos. Show all posts

Thursday, April 8, 2010

The Six Pillars of MOSS 2007


The Six Pillars of MOSS 2007   6 pillars of moss sharepoint

1. Collaboration
By integrating Workspaces, Tasks, Forums, Surveys, Blogs, RSS and Wikis, the platform builds on the wild success of the 2003 collaboration features while hitting the Web 2.0 check box items for the new wave of collaboration and knowledge management applications. Point players in this space — SocialText, BlogTronix, SuiteTwo, eTouch, BaseCamp, Automattic, etc. — will no doubt out perform in select areas, on a feature by feature comparison, but previous adoption rates, customizability, and convenience will carryMOSS a long way here.
2. Portal
A one stop site for everything enterprise-related. This concept is getting tired. Or maybe we're just tired of it. SharePoint is no longer branded as a “portal server” in the 2007 version (though the word is still in the product API Namespace). However, SharePoint still is a portal framework and web parts are still portlets. In fact, this remains one of the primary differentiators between the pay per CAL SharePoint version and the free WSS offering. Some new goodness with Master Pages, new flexibility with a pluggable Single Sign-on architecture, better search, and much improved Visual Studio integration will help on the portal side, but overall its not that exciting to talk about.
3. Enterprise Search
Search was a bit of a painful thing with SPS 2003, especially when it came to integrating various content stores. The core problems have been addressed and the functionality broadly expanded. MOSS 2007 opens up ACL-aware search across both local and remote data stores with features that enable specialized search for people and expertise. The ability to index and search data in line-of-business apps via the Business Data Store integration is powerful and will please both business managers and developers alike. The new “Best Bets” feature adds a new depth of intelligence — pulling search hits from entitled by not included search scopes. There's new meat here. We feel that in this 2007 release, SharePoint search is transforming from a check box to a compelling feature.
4. Web & Enterprise Content Management
This is the big one for us. Microsoft is including core document management, major and minor versioning, check-in/check-out document locking, rich descriptive metadata, workflow (via Windows Workflow Foundation), content type-based policies, auditing, and role-based-access controls at the document library, folder, and individual document levels. The 2007 release builds on these capabilities delivering enhanced authoring, business document processing, Web Content Management and publishing, records management (DoD 5015.2 certification coming soon), policy management, and support for multilingual publishing.
Whew. There's a lot happening here. There are several different MS engineering groups working away at these features. No question about it, the content management functionalities in MOSS have been expanded broadly and will continue to do so. ExistingMCMS customers considering a growth path will not necessarily find an easy migration story. With that said, the pathway there is evolving, MS' CM Assessment Tool is helpful, and the partner community — migration, integration, and customization — is pitching its significant weight in.
5. Forms Driven Business Process
Microsoft has overhauled this aspect of SharePoint with XML driven InfoPath forms that are available on a variety of platforms including portable wireless devices. Client/Server based form maintenance has been centralized and improved for business processes for partner and customers. This area is not as close to our hearts, but is another dynamic one that captures attention. As InfoPath gains momentum and additional integration evolves between Visual Studio, InfoPath, and SharePoint, I predict we will a strong uptick in the developer community.
6. Business Intelligence
Finally, BI has been improved across the board with web-based dashboards on the macro level, server-based Excel Services and Excel Web Services API's, line of business application and data repository integration, and more sophisticated abilities to monitor key performance indicators. Despite Microsoft's Performance Point BI server, this is one area of MOSS that we feel has the ability to shift the market. SharePoint 2003 transformed workgroup document storage and collaboration. We believe that SharePoint 2007 aims to do the same thing with BI. By enabling business users to build-out simple integration, dashboarding, andPKI monitoring MS are definitely looking for the next dimension for SharePoint growth.

Thursday, March 11, 2010

getting login username using c#.net code for asp.net web app

ad this line to .cs file ::   using System.Security.Principal;


copy this code in .cs file




protected void Page_Load(object sender, EventArgs e)
    {


        string a;


        a = System.Security.Principal.WindowsIdentity.GetCurrent().Name.ToString();
        string[] b = a.Split('\\');


        Label1.Text = b[1].ToString();
        string username = b[1].ToString();
        Label1.Text = username;
    }




in default.aspx page :


add this ::



then run it u will get user name in label. for more info plz do reply it or comment on it

Friday, February 26, 2010

Connection strings for Oracle


.NET Framework Data Provider for Oracle

Type:    .NET Framework Class Library
Usage:  System.Data.OracleClient.OracleConnection
Manufacturer:  Microsoft
More info about this class library »
Data Source=MyOracleDB;Integrated Security=yes;
This one works only with Oracle 8i release 3 or later
Specifying username and password
Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;Integrated Security=no;
Omiting tnsnames.ora
This is another type of Oracle connection string that doesn't rely on you to have a DSN for the connection. You create a connection string based on the format used in the tnsnames.ora file without the need to actually have one of these files on the client pc.
SERVER=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=MyHost)(PORT=MyPort))(CONNECT_DATA=(SERVICE_NAME=MyOracleSID)));uid=myUsername;pwd=myPassword;
Some reported problems with the one above and Visual Studio. Use the next one if you've encountered problems.
Data Source=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=MyHost)(PORT=MyPort))(CONNECT_DATA=(SERVICE_NAME=MyOracleSID)));User Id=myUsername;Password=myPassword;
Using Connection Pooling
The connection pooling service will create a new pool if it can't find any existing pool that exactly match the new connections connection string properties. If there is a matching pool a connection will be recycled from that pool.
Data Source=myOracleDB;User Id=myUsername;Password=myPassword;Min Pool Size=10;Connection Lifetime=120;Connection Timeout=60;Incr Pool Size=5;Decr Pool Size=2;
The first connection opened creates the connection pool. The service initially creates the number of connections defined by the Min Pool Size parameter.

The Incr Pool Size attribute defines the number of new connections to be created by the connection pooling service when more connections are needed.

When a connection is closed, the connection pooling service determines whether the connection lifetime has exceeded the value of the Connection Lifetime attribute. If so, the connection is closed; otherwise, the connection goes back to the connection pool.

The connection pooling service closes unused connections every 3 minutes. The Decr Pool Size attribute specifies the maximum number of connections that can be closed every 3 minutes.
Windows Authentication
Data Source=myOracleDB;User Id=/;
Privileged Connection
With SYSDBA privileges
Data Source=myOracleDB;User Id=SYS;Password=SYS;DBA Privilege=SYSDBA;
Privileged Connection
With SYSOPER privileges
Data Source=myOracleDB;User Id=SYS;Password=SYS;DBA Privilege=SYSOPER;
Utilizing the Password Expiration functionality
First open a connection with a connection string. When the connection is opened, an error is raised because the password have expired. Catch the error and execute the OpenWithNewPassword command supplying the new password.
Data Source=myOracleDB;User Id=myUsername;Password=myPassword;

oConn.OpenWithNewPassword(sTheNewPassword);
Proxy Authentication
Data Source=myOracleDB;User Id=myUsername;Password=myPassword;Proxy User Id=pUserId;Proxy Password=pPassword;

dotConnect for Oracle

Type:    .NET Framework Class Library
Usage:  Devart.Data.Oracle.OracleConnection
Standard
User ID=myUsername;Password=myPassword;Host=ora;Pooling=true;Min Pool Size=0;Max Pool Size=100;Connection Lifetime=0;

Microsoft OLE DB Provider for Oracle

Type:    OLE DB Provider
Usage:  Provider=msdaora
Manufacturer:  Microsoft
More info about this provider »
Standard security
This connection string uses a provider from Microsoft.
Provider=msdaora;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;
Trusted connection
Provider=msdaora;Data Source=MyOracleDB;Persist Security Info=False;Integrated Security=Yes;

Oracle Provider for OLE DB

Type:    OLE DB Provider
Usage:  Provider=OraOLEDB.Oracle
Manufacturer:  Oracle
More info about this provider »
Standard Security
Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;
Trusted Connection
This one specifies OS authentication to be used when connecting to an Oracle database.
Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;OSAuthent=1;
Oracle XE, VB6 ADO
Provider=OraOLEDB.Oracle;dbq=localhost:1521/XE;Database=myDataBase;User Id=myUsername;Password=myPassword;
Oracle XE, C++ ADO
Provider=OraOLEDB.Oracle;Data Source=localhost:1521/XE;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
TNS-less connection string
Provider=OraOLEDB.Oracle;Data Source=(DESCRIPTION=(CID=GTU_APP)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=myHost)(PORT=myPort)))(CONNECT_DATA=(SID=MyOracleSID)(SERVER=DEDICATED)));User Id=myUsername;Password=myPassword;
Controling rowset cache mechanism
Specifies the type of caching used by the provider to store rowset data. OraOLEDB provides two caching mechanisms; File and Memory.
Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;CacheType=File;
Memory is the default value. All the rowset data is stored in-memory which provides better performance at the expense of higher memory utilization.

File = All the rowset data is stored on disk. This caching mechanism limits the memory consumption at the expense of performance.
Controling the fetchsize
This one specifies the number of rows the provider will fetch at a time (fetch array).
Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;FetchSize=200;
The FetchSize value must be set appropriately depending on the data size and the response time of the network. If the value is set too high, this could result in more wait time during the execution of the query. If the value is set too low, this could result in many more round trips to the database. Valid values are 1 to 429,496,296. The default is 100.
Controling the chunksize
This one specifies the size, in bytes, of the data in LONG and LONG RAW columns fetched and stored in the provider cache.
Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;ChunkSize=200;
Providing a high value for this attribute improves performance, but requires more memory to store the data in the rowset. Valid values are 1 to 65535. The default is 100.
Using with Microsofts OLE DB .NET Data Provider
The Microsoft OLE DB .NET Data Provider can utilize OraOLEDB as the OLE DB Provider for accessing Oracle. However this must be enabled in the connection string.
Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;OLEDB.NET=True;
The OLEDB.NET connection string attribute must not be used in ADO applications.
Using OraOLEDB Custom Properties with Microsofts OLE DB .NET Data Provider
The SPPrmsLOB and NDatatype properties can only be set as connection string attributes when OraOLEDB is used by OLE DB .NET Data Provider.
Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;OLEDB.NET=True;SPPrmsLOB=False;NDatatype=False;SPPrmsLOB=False;
Using ADO, these properties would have been set as a property on the command. This is not possible if using the Microsofts OLE DB .NET Data Provider. So the properties are specified in the connection string instead.

PLSQLRSet: If the stored procedure, provided by the consumer, returns a rowset, PLSQLRSet must be set to TRUE (enabled).

NDatatype: This property allows the consumers to specify whether any of the parameters bound to the command are of Oracle's N datatypes (NCHAR, NVARCHAR or NCLOB). This information is required by OraOLEDB to detect and bind the parameters appropriately. This property should not be set for commands executing SELECT statements. However, this property must be set for all other SQLs such as INSERT, UPDATE, and DELETE.

SPPrmsLOB: This property allows the consumer to specify whether one or more of the parameters bound to the stored procedures are of Oracle's LOB datatype (CLOB, BLOB, or NCLOB). OraOLEDB requires this property to be set to TRUE, in order to fetch the parameter list of the stored procedure prior to execution. The use of this property limits the processing overhead to stored procedures having one or more LOB datatype parameters.
Using distributed transactions
This one specifies sessions to enlist in distributed transactions. This is the default behaviour.
Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;DistribTX=1;
Valid values are 0 (disabled) and 1 (enabled).