Month: December 2012

DotNetNuke Installation Guide

DotNetNuke is the Web Content Management Platform to build web sites and web application. Powered by the .NET development platform, DotNetNuke features powerful modules and interface making it stand apart from its CMS competitors.

This tutorial, being an introduction for establishing a DotNetNuke site, will take you through the important steps to get your site up and running.

This tutorial is for installation of DotNetNuke Community Edition.

For the purpose of introduction to DotNetNuke installation, the database instance used in the tutorial is SQL Server 2005 / 2008 / 2008R2 / 2012 Express with user instance database.

The operating system used to install is Windows Server 2008 R2.

Step 1: Requirements and Installation Media

The requirements for DotNetNuke are as follows:

  • Supported Operating Systems
    Windows XP
    Windows Server 2000
    Windows Server 2003
    Windows Vista
    Windows 7
    Windows 8
    Windows 2008
    Windows 2008 R2
  • Web Server
    Microsoft IIS 5.0, 5.1, 6.0, 7.0, 7.5, 8.0 
  • Database Server
    Microsoft SQL Server 2005
    Microsoft SQL Server 2008
    Microsoft SQL Server 2005 Express
    Microsoft SQL Server 2008 Express
    Microsoft SQL Server 2008 R2
    Microsoft SQL Server 2008 Express R2 
  • .NET Framework
    3.5 SP1
    4.0
    4.5 
  • Recommend Environment
    Windows Server 2008 R2
    IIS 7.5
    SQL Server 2008
    .NET Framework 3.5 SP1

Installation Media:

Obtain the installation media from the following link:

http://dotnetnuke.codeplex.com/releases/view/93277

In this tutorial, DotNetNuke 06.02.03 release is used.

Step 2: Prepare the DotNetNuke Environment.

    1. Once you’ve downloaded the latest stable release from the link provided above, extract the contents of the zip file to a folder on your computer.
    2. Create a directory in the C:\inetpub\wwwroot\ location named DNN.
    3. Copy the contents extracted from the package downloaded to this newly created directory.
    4. Right click on DNN directory; select properties. On the security tab, you’ll be presented with following screen.Ste2_4
    5. In this step, we will be adding the permissions for the appropriate user, in our case, as we are using Windows Server 2008 R2; we are required to add permissions for user “Network Service”.  Note: Windows XP uses the local ASPNET account, Win2003/Vista/2008/7 use the local Network Service account
    6. So, on the above screen, click on Edit. On the proceeding screen, click on Add. Now you will be able to see the following dialog box.Step2_6
    7. In the “Enter the object names to select:” field, type in “Network service”. Click on Check Names. You’ll be able to see Network Service underlined in the same field. This shows the user which you’ve entered is valid.
    8. Click Ok, you’ll be able to see the previous screen where Network Service will be listed under Groups or user names.
    9. Under permissions for NETWORK SERVICE, check select allow Full Control.
      Step2_9
    10. Click OK, also click OK on DNN properties screen! All OK!
    11. Now, it is time for the most crucial step in the DNN installation. IIS MANAGER!
    12. Click Start, goto Run.. And type in “inetmgr”.Step2_12
    13. You’ll be presented with a calm screen of IIS Manager.
    14. Expand Sites, you’ll be able to see the “Default Web Site”.Step2_14
    15. Expand it too!
      Step2_15
    16. Right click the directory, DNN. Select “Convert to Application”.
    17. Click OK on the dialog box that appears.
    18. Hooray! The necessary steps for preparing the environment are complete!

Let us move on to the next step where we’ll be installing the DotNetNuke.

Step 3: Installing DotNetNuke

 

  1. Browse to the site using http://localhost/DNN
  2. The following screen will be shown. Make sure under installation method, Typical is selected. Click Next to continue.Step3_2
  3. On the File Permissions screen, make sure you are able to see the following message-
    Your site passed the permissions check.
    Yes, you should be able to see it in green ONLY!
  4. Click Next to continue.
  5. Next Screen is the database connection configuration. We don’t have to do anything out here as the default option selected is SQL Express Database. Click Next.
  6. It will start building the database for your DNN site. It may take a while.
  7. When you’re able to see following screen, the installation of DotNetNuke site with database as SQL Express is DONE!!Step3_7
  8. Click Next to contiue.
  9. Next screen will let you set a host account for DNN site.
  10. Enter the password, a valid e-mail address to finish the installtion. Click Next to finish.

Your DNN site is created, the Getting Started screen is shown.

As described initially, this guide is for the DotNetNuke installation with SQL Server 2005 / 2008 / 2008R2 / 2012 Express with user instance database.

In the next edition of the DotNetNuke guide, I’ll be taking you through the DotNetNuke installation with SQL Server 2005 / 2008 / 2008R2 / 2012 or Express edition with attached database.

🙂 🙂  Happy New Year 2013 🙂 🙂  !!

 

Advertisements

Top Myths About Cloud Computing

Cloud computing has been a hot topic during the last few years for technology specialists all over the world. Cloud computing has been adopted by many enterprises, but still challenges continue to rise. With all the articles and documentation on this subject, there are many myths that have developed over time. So here are the most common myths regarding cloud computing: security, data loss and performance.

Security is compromised in the cloud

Without a doubt, this is the most talked about point. In order to be a successful service provider, cloud providers have to assure the customers or prospects that their data is secure. The security risks that exist in the cloud are no different than the ones that exist in-house. The greatest advantage when outsourcing to cloud is that providers are permanently focused on improving controls and procedures so that the data is always secure, while enterprises might neglect this focus from time to time. So one could argue that a risk could be to remain in a physical environment. Most cloud computing providers also offer the customer different levels of security protection, which allows for more enhanced security.

You lose control of data in the cloud

This is another common myth. Most people think that they will not be able to access their data whenever they need because they cannot see the actual physical drive’s that the data is being stored on. With the Cloud, the technology maintenance and support issues are in the hands of the cloud hosting provider, which means a high level of availability and data.  Data in cloud environments is segmented and encrypted and some providers also allow you to control how your data is stored, which would allow your data to be on a shared storage system or dedicated storage.  I have worked with these types of cloud systems and think that flexibility is the future of cloud management.

Performance is a problem in the cloud

It is easier to add additional resources in a cloud environment and if deployed correctly, those resources can be balance and enable you to achieve a higher level of performance and redundancy. The latest servers built for the cloud, like the Cisco UCS that I’m familiar with run on very high performance blades that most companies do not deploy in a physical environment which has allowed us to achieve much more performance over the same systems in a physical environment.  There could be some refactoring of your db’s and applications to take advantage of the cloud to receive the same benefits we have received above.

Creating Your First Yii Application

Hello everyone. In this tutorial we will be looking at setting up the Yii framework and create our skeleton app step by step. Lets begin.

Firstly, we need to download the Yii framework. This can be done from the Yii Framework website. When the download is complete, unzip the file and you will see a folder containing:

  • demos
  • framework
  • requirements
  • and some legal mumbo jumbo & other stuff

The only folder we are interested in is the framework folder. Copy this folder and go to your localhost. Paste the yii framework folder in a new folder where we are going to setup our application, in this tutorial we are using: localhost/yii-demo

Cool, Now open up your command prompt and navigate to the localhost/yii-demo/framework (e.g : c:\wamp\www\yii-demo\framework

Now type in:  yiic webapp c:\wamp/www/myFirstYiiApp This will ask you if you want to “Create we application under ‘C:\wamp\www\myFirstYiiApp’? [Yes:No]“
We do want to so type in “yes”. Some of you might get an error at this point saying something about php or something like that (great tutorial right?). That simply means you don’t have php setup as an environment variable.

To fix this:
“Open the Environment Variables window by going to: Start -> My Computer (right click!) -> Advanced Tab -> Environment Variables -> Click Path in System variables -> Edit.

In Windows 7, press the Win key and type “env”. You should see a control panel section with a shortcut to “Edit the system environment variables”. Select it and then click on “Environment Variables…”
Click on the variable called PATH and click “Edit…”. Do not delete the paths already there! Separate each path with semicolons.
Now you have to add the following PATHs in Windows: “C:\wamp\bin\php\php5.2.8″ and “C:\wamp\www\yii-demo\framework”. The former path should lead where your php.exe resides, and the latter where your yiic.bat resides.”
That bit is stolen from the Yii wiki page, thanks.
So we have type yes (or simply Y) and we should see a whole bunch of lines of stuff happening and the message “Your application has been created under C:\wamp\www\myFirstYiiApp ”. We have now created our skeleton app.
If you point your browser at localhost/myFirstYiiApp you should see the Yii skleton app. Well done, you have just installed Yii.

Some Basic Tips To Speed Up Your MySQL Queries

If you are interested in how to create fast MySqlqueries, this article is for you

1.    Use persistent connections to the database to avoid connection overhead.

2.    Check all tables have PRIMARY KEYs on columns with high cardinality (many rows match the key value). Well,`gender` column has low cardinality (selectivity), unique user id column has high one and is a good candidate to become a primary key.

3.    All references between different tables should usually be done with indices (which also means they must have identical data types so that joins based on the corresponding columns will be faster). Also check that fields that you often need to search in (appear frequently in WHERE, ORDER BY or GROUP BY clauses) have indices, but don’t add too many: the worst thing you can do is to add an index on every column of a table (I haven’t seen a table with more than 5 indices for a table, even 20-30 columns big). If you never refer to a column in comparisons, there’s no need to index it.

4.    Using simpler permissions when you issue GRANT statements enables MySQL to reduce permission-checking overhead when clients execute statements.

5.    Use less RAM per row by declaring columns only as large as they need to be to hold the values stored in them.

6.    Use leftmost index prefix — in MySQL you can define index on several columns so that left part of that index can be used a separate one so that you need less indices.

7.    When your index consists of many columns, why not to create a hash column which is short, reasonably unique, and indexed? Then your query will look like:

8.    Consider running ANALYZE TABLE (or myisamchk –analyze from command line) on a table after it has been loaded with data to help MySQL better optimize queries.

9.    Use CHAR type when possible (instead of VARCHAR, BLOB or TEXT) — when values of a column have constant length: MD5-hash (32 symbols), ICAO or IATA airport code (4 and 3 symbols), BIC bank code (3 symbols), etc. Data in CHAR columns can be found faster rather than in variable length data types columns.

10.    Don’t split a table if you just have too many columns. In accessing a row, the biggest performance hit is the disk seek needed to find the first byte of the row.

11.    A column must be declared as NOT NULL if it really is — thus you speed up table traversing a bit.

12.    If you usually retrieve rows in the same order like expr1, expr2, …, make ALTER TABLE … ORDER BY expr1, expr2, … to optimize the table.

13.    Don’t use PHP loop to fetch rows from database one by one just because you can — use IN instead

14.    Use column default value, and insert only those values that differs from the default. This reduces the query parsing time.

15.    Use INSERT DELAYED or INSERT LOW_PRIORITY (for MyISAM) to write to your change log table. Also, if it’s MyISAM, you can add DELAY_KEY_WRITE=1 option — this makes index updates faster because they are not flushed to disk until the table is closed.

16.    Think of storing users sessions data (or any other non-critical data) in MEMORY table — it’s very fast.

17.    For your web application, images and other binary assets should normally be stored as files. That is, store only a reference to the file rather than the file itself in the database.

18.    If you have to store big amounts of textual data, consider using BLOB column to contain compressed data (MySQL’s COMPRESS() seems to be slow, so gzipping at PHP side may help) and decompressing the contents at application server side. Anyway, it must be bench-marked.

19.    If you often need to calculate COUNT or SUM based on information from a lot of rows (articles rating, poll votes, user registrations count, etc.), it makes sense to create a separate table and update the counter in real time, which is much faster. If you need to collect statistics from huge log tables, take advantage of using a summary table instead of scanning the entire log table every time.

20.    Don’t use REPLACE (which is DELETE+INSERT and wastes ids): use INSERT … ON DUPLICATE KEY UPDATE instead (i.e. it’s INSERT + UPDATE if conflict takes place). The same technique can be used when you need first make a SELECT to find out if data is already in database, and then run either INSERT or UPDATE. Why to choose yourself — rely on database side.

21.    Tune MySQL caching: allocate enough memory for the buffer (e.g. SET GLOBAL query_cache_size = 1000000) and define query_cache_min_res_unit depending on average query resultset size.

22.    Divide complex queries into several simpler ones — they have more chances to be cached, so will be quicker.

23.    Group several similar INSERTs in one long INSERT with multiple Values lists to insert several rows at a time: query will be quicker due to fact that connection + sending + parsing a query takes 5-7 times of actual data insertion (depending on row size). If that is not possible, use START TRANSACTION and COMMIT, if your database is InnoDB, otherwise use LOCK TABLES — this benefits performance because the index buffer is flushed to disk only once, after all INSERT statements have completed; in this case unlock your tables each 1000 rows or so to allow other threads access to the table.

24.    When loading a table from a text file, use LOAD DATA INFILE (ormy tool for that), it’s 20-100 times faster.

25.    Log slow queries on your dev/beta environment and investigate them. This way you can catch queries which execution time is high, those that don’t use indexes, and also — slow administrative statements (like OPTIMIZE TABLE and ANALYZE TABLE)

26.    Tune your database server parameters: for example, increase buffers size.

27.    If you have lots of DELETEs in your application, or updates of dynamic format rows (if you have VARCHAR, BLOB or TEXT column, the row has dynamic format) of your MyISAM table to a longer total length (which may split the row), schedule running OptimizeTABLE query every weekend by crone. Thus you make the defragmentation, which means more speed of queries. If you don’t use replication, add LOCAL keyword to make it faster.

28.    Don’t use ORDER BY RAND() to fetch several random rows. Fetch 10-20 entries (last by time added   or  ID) and make array_random() on PHP side. There are also other solutions.

29.    Consider avoiding using of HAVING clause — it’s rather slow.

30.    In most cases, a DISTINCT clause can be considered as a special case of GROUP BY; so the optimizations applicable to GROUP BY queries can be also applied to queries with a DISTINCT clause. Also, if you use DISTINCT, try to use LIMIT (MySQL stops as soon as it finds row_count unique rows) and avoid ORDER BY (it requires a temporary table in many cases).

31.    When I read “Building scalable web sites”, I found that it worth sometimes to de-normalise some tables (Flickr does this), i.e. duplicate some data in several tables to avoid JOINs which are expensive. You can support data integrity with foreign keys or triggers.

32.    If you want to test a specific MySQL function or expression, use Benchmark function to do that.

HelloWorld iOS application

Hi folks,

This is very first post about iPhone app development .

I assume you people are familiar with basic of objective c and cocoa framework and Xcode.

So this post bring you the anatomy of first HelloWorld  application

let’s start…

Prerequisites

1. Xcode

2.basic of  objective c and iphone SDK

last and foremost  patience 🙂

Here are the following steps you need to build your HelloWorld application

1.Create new XCode Project

  Create your  project going through XCode ->File ->New Project and select  Empty Application .Name the project HelloWorld and click Save as shown in figure

XCode will create two file AppDelegate.h and AppDelegate.m . Difference between .h and .m file is in objective c all declaration goes to  .h file and implementation goes to .m file.

Now What  is AppDelegate  actually?

When you create your  project, main.m file under  Supporting files is generated by XCode

it looks like

#import <UIKit/UIKit.h>

int main(int argc, char *argv[])

{

    NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];

    int retVal = UIApplicationMain(argc, argv, nil, nil);

    [pool release];

    return retVal;

}

 as in any C program the execution of Objective -c application starts from main().the main() function starts by creating autorelease pool and ends by releasing it. In between it makes a call to the UiApplicationMain() function. UiApplicationMain() is declared as follows

int UIApplicationMain(int argc, char *argv[], NSString *principalClassName, NSString *delegateClassName);

The UiApplicationMain() instantiate the application and the application delegate objects. after that,it sets the delegate property of the application object to the application delegate instance.

The Typical application delegate class looks like

#import <UIKit/UIKit.h>

@interface AppDelegate : NSObject <UIApplicationDelegate>

{}

@end

Notice that application delegate class inherits NSObject class and adopts UIApplicationDelegate protocol and implements the UIApplicationDelegate methods.One of the very first  method of UiApplicationDelegate is

 – (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions{}

This method is starting point for developer didFinishLaunchinWithOptions is application life cycle method it is called when application will launch (onCreate() in Android )

Note : NSObject is the super class of all classes available in objective c and Protocol is  here interface 

 – (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions

{

    self.window = [[[UIWindow alloc] initWithFrame:[[UIScreen mainScreen] bounds]] autorelease];

    // Override point for customization after application launch.

    self.window.backgroundColor = [UIColor whiteColor];

    [self.window makeKeyAndVisible];

    return YES;

}

 above code simply illustrate that when application will launch  a new window will be allocated by

self.window = [[[UIWindow alloc] initWithFrame:[[UIScreen mainScreen] bounds]] autorelease];
and  set its background color to white by
self.window.backgroundColor = [UIColor whiteColor];
at last make it visible.

 2. Create User Interface using code 

 For your application very first object you need is appdelegate class which we have been seen above

now suppose you application has more than one screen so how will you create your screen(View)?

In iphone each screen is   ViewController (in Android Activity).

For this create a simple class which is a subclass of UIViewController going through

right click on AppDelegate.h  >>>newFile  >>Cocoa Touch >> UiViewController subclass >>next.

Name the file  and create it.

 3. Create object of your newly created UIViewController and add it to the main Window.

 modify AppDelegate.h file with following piece of code

#import <UIKit/UIKit.h>

#import “HelloWorldViewController.h”

 @interface AppDelegate : UIResponder <UIApplicationDelegate>

{

    HelloWorldViewController *helloWorldVC;

}

@property (strong, nonatomic) UIWindow *window;

@end

modify AppDelegate.m file
– (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions

{

    self.window = [[[UIWindow alloc] initWithFrame:[[UIScreen mainScreen] bounds]] autorelease];

    // create viewcontroller object

    helloWorldVC=[[HelloWorldViewController alloc]init];

   //add it to the window

    [self.window addSubview:helloWorldVC.view];

    [self.window makeKeyAndVisible];

    return YES;

}

what you have done so far is you have created  HelloWorldViewController and added it to main window. now create label in your controller

4.Create UiLabel and add it to HelloWorldViewController
  •  Open HelloWorldViewController.h file and declare UILabel
#import <UIKit/UIKit.h>
@interface HelloWorldViewController : UIViewController
{

    UILabel *label;

}

@end
  •  Open HelloWorldViewController.m file create label and set it’s property

#import “HelloWorldViewController.h”

 @implementation HelloWorldViewController

– (id)init

{

    self = [super init];

    if (self) {

        label=[[UILabel alloc]initWithFrame:CGRectMake(100, 250, 200, 30)];

        label.text=@”HelloWorld”;

    }

    return self;

}

  •  Add label to ViewController

-(void)loadView

{

    [super loadView];

    [self.view addSubview:label];

}

5. Build and Run

Run your project by clicking run button (top left corner in XCode).

 enjoy coding……

Feel free to comment .For any query mail me @ bpsingh@pmtsl.onmicrosoft.com