Monday, September 17, 2012

What’s New in vSphere 5.1 – Networking

With the release of VMware vSphere 5.1, VMware brings a number of powerful new features and enhancements to the networking capabilities in the VMware vSphere platform. The following diagram provides a list of new features in different categories
Read more »
Posted by at No comments:

Sunday, September 9, 2012

How To Add A READ MORE Option To Your Blogspot Posts:Blogger

Would you like to have an option, or a way, to make your Blogger posts on your Home Page,have a 'Read more..' text or button, in case they get too long?..If Yes, sit back and keep reading..

The "Read More" feature, also called "Jump Break" is a feature which lets you create expandable post summaries in your blog posts, so longer posts appear as an intro with a link to Read More. With Jump Breaks you can show just a snippet of your post on your blog's home page. Blogger will insert a "Read more" link to the full post page where your readers can keep reading.

If you go to the home page of my blog( http://sarkari-naukari-job.blogspot.in/ ), you will see that each blog post on the page has a READ MORE link, which after been clicked on, will take the reader to the full post page where the reader can read the full post.

love using the READ MORE feature because I believe it makes it easier for my blog readers to scan through the main topics on the home page. More so, it makes my blog home page to load faster. I cherish simplicity a lot...
So, How Do I Get Started ?

There are a couple of ways to insert a "Read more" jump to your posts. Before we go into that, I will like you to activate post pages and set it to, probably 5 posts on the main page. To do this, login to your blogger dashboard, go to SETTINGS > FORMATING and set the "show at most" option to "5 posts on the main page". You can choose any number you desire though.

Read more »
Posted by at 1 comment:

Thursday, April 12, 2012

Interview Question ‘N’ Answer Bank For IT


Q.1 What is the latest Service Pack for Exchange 2000?

Ans : Service Pack 3.

Q.2 What are the versions of ISA servers and their service packs?

Ans :  ISA Server 2000 SP1
           ISA Server 2004 SP1

Q.3 What are the core services that run a ISA server?

Ans : Microsoft ISA Server Control
          Microsoft Web Proxy

Read more »
Posted by at No comments:

Unix Interview Qus & Ans


User
These questions will demonstrate whether the supplicant has had exposure to UNIX as an end-user. Does not imply that the user has any other skills, only that they've really used

UNIX.
___ List 10 UNIX Commands List 10 UNIX Commands

___ What is the most important UNIX command? Man

___ How do I create a directory? Mkdir

___ How do I find out what processes are running? ps, top

___ How do I exit Emacs/How do I exit vi? ^C^X for Emacs, :q for vi

___ What does the grep command do? searches files or streams for a regex

___ How do I stop a process? kill

Read more »
Posted by at No comments:

Technical round Interview Help Tips




Technical round

ADS Overview,
definitions of
Trees, Forest, Domain, Organizational Unit, Global Catalog, Sites, Domain Controller,
you will have to explain him the differences between any of the asked question.

make sure that you know the FSMOS roles, that is Schema Master, RID Master, Domain Naming Master, PDC Emulator Master and Infrastructure Master.

the basic of Exchange server Administrator, like
How to create address list,users.
How to install Exchange server,
Requirements for installing Exchange server.
Why do we run forestprep, domainprep before actually installing exchange server.
The basic of TCPIP, Routing Protocols, Nat, Subnet, Layer3 Switch, Layer2 Switch, Hub, Router.

You should be aware of the
DNS Integration with Active Directory and also DHCP
authorizing with Active directory.

What Is system state backup?
Difference between admin groups and routing groups?
Difference between  incremental and differential backup?
What is DNS?
What are forward Look up and reverse lookup?
What is difference between 10 base 2 and 10 base 5 cable?
UR overall job profile in current industry
How to GC in new additional domain controller?(Pocedure how u practically do it)?

Posted by at No comments:

Tuesday, April 3, 2012

How to make ISA server 2004



 Today’s a big day here at www.isaserver.org. That’s right, today ISA Server 2004 beta 2 was released to the public. Yes, that’s right, beta 2. Earlier betas were done in a private beta testing group, so that you wouldn’t be exposed to problems you usually see in beta 1 releases. The good news is that the beta 2 version has been out for a few weeks already, and it’s pretty reliable and just about all the features work how they say they do.
You can head over to the Microsoft Web site and download the ISA Server 2004 Beta 2 software at http://www.microsoft.com/isaserver/beta/default.asp. If you’re like me and most others I know in the ISAServer.org community, you’ll want to install the software and kick the tires as soon as possible. For that reason, I’ll hold off on the review of new features and functionality included in ISA Server 2004 until later this week. What you want to do is get ISA Server 2004 up and running now!
First, some suggestions:
  • This is beta software, so don’t go installing it as your production firewall and expect your users to be happy
  • You can install ISA Server 2004 on Windows 2000 or Windows Server 2003. I highly recommend that you install on Windows Server 2003, but that’s up to you
  • ISA Server 2004 applies firewall policy on all interfaces, so things are going to work a lot differently than they did with ISA Server 2000. Be patient, you’re going to love it, just realize that it works a LOT differently than ISA Server 2000
  • After installing ISA Server 2004, spend some time looking around the new user interface. It’s completely different than what you’ve seen in ISA Server 2000, so don’t expect to immediately move your ISA Server 2000 skills over to ISA Server 2004. The good news is that it’s a lot easier to create Access Policy in ISA Server 2004 than it was in ISA Server 2000
  • And here’s a treat for you DMZ fans: you can easily create multiple private address DMZs – no more LAT-based DMZ kludges! In fact, the LAT is gone
    •  Stephen Chetcuti and I will be working on Web boards dedicated to ISA Server 2004, but until then, just post your questions to the Web boards at http://forums.isaserver.org in the appropriate section and make a note in the title of the post that it refers to ISA Server 2004 and I’ll give it priority!
    Now let’s get to business. In this article we’ll go over the following steps to get you up and running:
  • Installing Windows Server 2003 and setting up the supporting network infrastructure
  • Installing ISA Server 2004
  • Viewing the System Policy
  • Creating an "All Open" outbound Access Policy
  • Blocking downloads using HTTP Filtering
    •  We’re only going to scratch the surface of ISA Server 2004 today. Expect tons of articles on ISA Server 2004 beta 2 over the next couple of months. Don’t worry – Debi and I will have a book for you soon enough. But until then, stay tuned here at www.isaserver.org for news, tutorials, help and support for ISA Server 2004 beta 2. Also, keep your eye out for the Reviewer’s Guide at the Microsoft Web site (www.microsoft.com/isaserver). It has a fantastic section with a lot of walk-throughs that will familiarize you with the new interface and almost all the new features included in ISA Server 2004.
    Like ISA Server 2000, ISA Server 2004 has modest hardware requirements. You can install ISA Server 2004 on any machine with a Pentium III 500+ MHz processor with at least 256MB of RAM. Of course, I recommend that you increase the processor speed and memory to as much as you can afford, but you don’t need a PC that can run the starship Enterprise to run ISA Server 2004.
    The machine should have at least two network interface cards. One of the cards is the external interface and the other card will be the internal interface. Unlike ISA Server 2000, there is no Local Address Table, so you can install multiple internal interface cards to create multiple internal networks, in addition to multiple public or private address DMZs. Firewall Access Policy controls traffic moving between all network interface cards.
    The test network used in the discussion in this article is configured as shown below. The ISA Server 2004 firewall is located behind a DSL router, and the external interface of the ISA Server 2004 firewall uses the LAN address of the DSL router as its default gateway.



    I have not yet tested ISA Server 2004 using a dial-up interface, so I won’t be covering that configuration in this article. I’ll be very interested in your experiences using a dial-up interface with ISA Server 2004, so if you’re using a dial-up interface, make sure to post your experiences with using a dial-up interface over at the Web boards at http://forums.isaserver.org.
    As with all firewall installations, DNS and DHCP are critical factors in making sure that everything works correctly. You can install a DNS server on the ISA Server 2004 firewall computer and use it to connect to the Internet, or you can use a DNS server located on your internal network. In this example, we will install a DNS server on the ISA Server 2004 firewall and configure your client located behind the ISA Server 2004 firewall to use the ISA Server 2004 DNS server as its DNS server.
    DHCP is a bit stickier. You can install a DHCP server on the ISA Server 2004 machine, but there is a beta issue where you need to allow all networks access to inbound DHCP REQUEST messages. For this reason, external hosts can send DHCP REQUEST messages to the DHCP server on the ISA Server 2004 firewall. While the firewall is not required to send a reply to these hosts, there are potential security risks with allowing these inbound DHCP REQUEST messages. This problem should be fixed by the time the software is finalized. At this time, I recommend that you do not install a DHCP server on the ISA Server 2004 firewall machine until this problem is addressed. If you want to use DHCP, install a DHCP server on the internal network.
    Perform the following steps to install the DNS server on the Windows Server 2003 machine that will be the ISA Server 2000 firewall. If you already have a DNS server on your network that can resolve Internet host names, then you do not need to perform these steps and you can configure your clients to use your current DNS server:
    1. Click Start and point to Control Panel. Click the Add/Remove Programs entry.
    2. In the Add or Remove Programs window, click the Add/Remove Windows Components button on the left side of the window.
    3. In the Windows Components page, click on the Networking Services entry in the Components list and click Details.
    4. In the Networking Services dialog box, put a checkmark in the Domain Name System (DNS) checkbox and click OK.
    5. Click Next on the Windows Components page.
    6. Point the installer to the Windows Server 2003 installation files when asked.
    7. Click Finish on the Completing the Windows Components Wizard page.
    At this point the DNS server is listening on all interfaces. That isn’t a problem because there will be no Access Policy that enables inbound access to the DNS server for external hosts.

    Installing ISA Server 2004

    The next step is to install the ISA Server 2004 software. Setup is relatively straightforward, but we’ll go through the steps in detail to make sure you understand what’s happening.
    Perform the following steps to install the ISA Server 2004 software on the dual-homed Windows Server 2003 machine:
    1. Download the ISA Server 2004 beta 2 software from http://www.microsoft.com/isaserver/beta/default.asp. When you run the exe file, it will create a folder on your C: drive containing the installation files. Double click on the isaautorun.exe file.
    2. On the Microsoft Internet Security and Acceleration Server 2004 Beta 2 Setup page, click the link for Review Release Notes and read the release notes. The doc isn’t that long, and you’ll get some useful information about what works and what doesn’t, as well as some useful tips on how to access the Internet from the ISA Server 2004 firewall machine itself. After reading the release notes, click the Read Setup and Feature Guide link. You don’t need to read the entire guide right now, but you might want to print it out to read later. Click the Install ISA Server 2004 link.
    3. Click Next on the Welcome to the Installation Wizard for Microsoft ISA Server 2004 Beta 2 page.
    1. Select the I accept the terms in the license agreement option on the License Agreement page. Click Next.
    2. On the Customer Information page, enter your name and the name of your organization in the User Name and Organization text boxes. The Product Serial Number is automatically entered for you. Click Next.
    3. On the Setup Type page, select the Custom option. If you do not want to install the ISA Server 2004 software on the C: drive, then click the Change button to change the location of the program files on the hard disk. Click Next.

    1. On the Custom Setup page you can choose which components to install. By default, the Firewall Services, ISA Server Management and Firewall Client Installation Share are installed. The Message Screener, which is used to control spam and file attachments from entering and leaving the network, is not installed by default. You need to install the IIS 6.0 SMTP service on the ISA Server 2004 firewall computer before you install the Message Screener. I will do some articles in the near future on how to install the Message Screener on the ISA Server 2004 firewall to control inbound and outbound flow of spam and email attachments. Use the default settings and click Next.

    1. On the Internal Network page, click the Add button. The Internal network is different than how the LAT was used in ISA Server 2000. In the case of ISA Server 2004, the internal network contains trusted network services that the ISA Server 2004 firewall must communicate with. Examples of such services include Active Directory domain controllers, DNS, DHCP, terminal services clients, and others. The firewall System Policy is automatically applied to the Internal network. We will look at the System Policy later in this article.

    1. In the Internal Network setup page, click the Configure Internal Network button.

    1. In the Configure Internal Network dialog box, remove the checkmark from the Add the following private ranges… checkbox. Leave the checkmark in the Add address ranges based on the Windows Routing Table checkbox. Put a checkmark in the checkbox next to the adapter that is connected to the Internal network. Click OK.

    1. Click OK in the dialog box informing you that the Internal network was defined, based on the Windows routing table.

    1. Click OK on the Internal network address ranges dialog box.

    1. Click Next on the Internal Network page.

    1. Click Install on the Ready to Install the Program page.
    2. On the Installation Wizard Completed page, put a checkmark in the Invoke ISA Server Management when wizard closes checkbox and click Finish.

    1. The Microsoft Internet Security and Acceleration Server 2004 management console opens. By default you are taken to the top node in the left pane of the console. Notice that ISA Server 2004 console requires quite a bit more screen real-estate than ISA Server 2000 did. To get the most out of the interface, change your screen resolution to 1024x768 or higher. I will need to keep the resolution at 640x480 for these screen shots to make them fit the Web page. For that reason, I will use the Show/Hide Console Tree button in the button bar of the console frequently.

    Viewing the System Policy

    By default, ISA Server 2004 does not allow outbound access to the Internet and does not allow Internet hosts to access the firewall. However, a default firewall System Policy is installed that allows network management tasks to be completed.
    Perform the following steps to see the default firewall System Policy:
    1. In this Microsoft Internet Security and Acceleration Server 2004 management console, expand the server node in the scope pane (left pane) and click on the Firewall Policy node. Right click on the Firewall Policy node, point to View and click Show System Rules.

    1. Click the Show/Hide Console Tree button and then click the Open/Close Task Pane arrow (the little blue arrow on the left edge of the task pane on the right side of the console). Notice that the ISA Server 2004 Access Policy represents an ordered list. Policies are processed from top to bottom, which is a significant departure from how ISA Server 2000 processed Access Policy. The System Policy represents a default list of rules that controls access to and from the ISA Server 2004 firewall by default. Scroll down the list of System Policy Rules. Notice that the rules are defined by:
    Order number
    Name
    Action (allow or deny)
    Protocols
    From (source network or host)
    To (destination network or host)
    Condition (who or what the rule applies to)     You may want to widen the Name column to get a quick view of the rules. Notice that not all the rules are enabled. System Policy Rules that are disabled by default have a tiny down-pointing red arrow in their lower right corner. The disabled System Policy Rules will become automatically enabled when you make configuration changes to the ISA Server 2004 firewall, such as when you enable VPN access.
    Notice that one of the System Policy Rules allows the firewall to perform DNS queries to DNS servers on all networks.

    1. Review the System Policy Rule and then hide the rules by clicking the Show/Hide System Policy Rules button in the console’s button bar. This is the depressed (pushed in) button seen in the figure below.

    Creating an "All Open" Outbound Access Policy

    The first thing most of you will want to do is see if the ISA Server 2004 is actually working. You can do this by creating an "all open" outbound access policy that allows SecureNAT clients to access the Internet. It’s important to keep in mind that this "all open" outbound access policy is for testing only. Secure networks do not allow all traffic outbound, and users should be given access only to the protocols they require. This is the difference between an ISA Server 2004 firewall and your old traditional packet filter based firewall!
    Perform the following steps to create the "all open" outbound access policy:
    1. In the Microsoft Internet Security and Acceleration Server 2004 management console, click the Show/Hide Console Tree button to expose the scope pane. Right click the Firewall Policy node, point to New and click Access Rule.

    1. On the Welcome to the New Access Rule Wizard page, enter All Open Outbound in the Access policy rule name text box. Click OK.

    1. On the Rule Action page, select the Allow option, then click Next.

    1. On the Protocols page, select the All outbound protocols option and click Next.

    1. On the Access Rule Sources page, click the Add button. In the Add Network Entities dialog box, click on the Networks folder. Double click on the Internal network, then click the Close button in the Add Network Entities dialog box. You may want to click on each of the folders so that you can see the Network Entities that come predefined with the ISA Server 2004 firewall. These Network Entities give you very fined tuned control over inbound and outbound access control. Click Next in the Access Rule Sources dialog box.

    1. Click the Add button on the Access Rule Destinations page. In the Add Network Entities dialog box, click the Networks folder. Double click the External entry and click Close in the Add Network Entities dialog box. Click Next on the Access Rule Destinations page.

    1. On the User Sets page, accept the default setting of All Users. ISA Server 2004 enables you to create custom user sets based on Active Directory or local SAM groups. This enables the firewall administrator to create custom firewall user groups without requiring access to the Active Directory and creating groups there. Click Next.

    1. Review your settings and click Finish on the Completing the New Access Rule Wizard page.
    2. Click the Apply button to save the changes and update the firewall policy. This button is located at the top of the Details pane (the middle pane) of the console. This Apply button enables you to make multiple changes to the firewall policy before they are applied. Change take place immediately after you click the Apply button.
    3. Click the Show/Hide Console Tree button so that you can expose the entire line of the Access Policy in the Details pane.

    Internal network clients now have full access to the Internet. SecureNAT clients have access to all protocols listed in the Protocols list in the Firewall Policy toolbox. Perform the following steps to view the Firewall Policy toolbox:
    1. In this Microsoft Internet Security and Acceleration Server 2004 management console, expose the scope pane if it is not visible by using the Show/Hide Console Tree button.
    2. If the Task Pane is not visible in the right side of the console, click the Open/Close Task Pane button.
    3. In the Task Pane, click the Toolbox tab. Click on the Protocols label. You will see protocols grouped into logical groups. Click on the All protocols folder. This displays a list of all the predefined protocols on the ISA Server 2004 firewall. You can create your own protocols if you like later. SecureNAT clients have access to all these protocols. SecureNAT client access to complex protocols still requires an application filter. Firewall clients can access all protocols, even those not included in this list (including complex protocols).

    The next rule we need to create is an Access Policy that allows Internal network clients to connect to the DNS sever on the ISA Server 2004 firewall. Remember, ISA Server 2004 is different from ISA Server 2000; Access Policy is applied to all interfaces, so the Internal network interface is protected just like all other interfaces.
    Perform the following steps to create the DNS rule that allows Internal network clients DNS access:
    1. Click the Show/Hide Console Tree button to expose the scope pane. Right click on the Firewall Policy node, point to New and click Access Rule.
    2. In the Welcome to the New Access Rule Wizard page, enter DNS from Internal Network in the Access policy rule name text box. Click Next.
    3. Select Allow on the Rule Action page and click Next.
    4. On the Protocols page, select the Selected protocols option from the This rule applies to list. Click the Add button.
    5. In the Add Protocols dialog box, click the Infrastructure folder. Double click on the DNS protocol and click Close in the Add Protocols dialog box. Click Next on the Protocols page.

    1. On the Access Rule Sources page, click Add. Click on the Networks folder and then double click on the Internal network. Click Close in the Add Network Entities dialog box. Click Next on the Access Rule Sources page.
    2. On the Access Rule Destinations page, click the Add button. In the Add Network Entities dialog box, click the Networks folder. Double click on the Local Host entry. Click Close in the Add Network Entities dialog box. Click Next on the Access Rule Destinations page.

    1. Accept the default entry of All Users on the User Sets page. Click Next.
    2. Click Finish on the Completing the New Access Rule Wizard page.
    3. Click Apply to save the changes and update the firewall policy.

    Create an HTTP Policy that Prevents HTTP Downloads

    ISA Server 2004 HTTP Policy allows you to get very fined-tuned control over what users can access via the HTTP protocol. HTTP policy can be used to prevent users from accessing any site, any content, and any protocol that might be tunneled in an HTTP header. In the future we will go over the details of HTTP Policy, but in this introductory article, we’ll see how you can quickly and easily prevent users from downloading Windows executables using HTTP. Note that HTTP policy will not look inside .zip files to determine if a Windows executable is inside it.
    Perform the following steps to configure HTTP Policy to prevent access to Windows executable files:
    1. Right click on the All Open Outbound Access Policy and click on the Configure HTTP command.

    1. On the General tab of the Configure HTTP policy for rule dialog box, put a checkmark in the Block responses with Windows executable content checkbox. Click Apply, then click OK.

    1. Click the Apply button to save the changes and update the firewall policy.
    Now let’s test the policy from an internal network client. The internal network client is a SecureNAT client, which means that it is not a Web Proxy or Firewall client. The default gateway on the client is set to the internal IP address on the ISA Server 2004 firewall. The DNS server setting on the client is also configured as the internal IP address on the ISA Server 2004 firewall.
    Perform the following steps on the SecureNAT client behind the ISA Server 2004 firewall computer:
    1. Open Internet Explorer and go to the www.isaserver.org Web site. Great! You were able to access the site.
    2. Now to the Web site http://www.microsoft.com/downloads/details.aspx?FamilyID=2f92b02c-ac49-44df-af6c-5be084b345f9&DisplayLang=en and scroll down to the bottom of the page. Click the link for isafp1.exe.

    1. The ISA Server 2004 firewall blocks the request because the HTTP Policy is configured to block access to Windows executable files. Close the Web browser.
    Posted by at No comments:

    VMware vCenter Configuration Manager - Voted VirtualizationAdmin.com Readers' Choice Award Winner - Monitoring, Management & Performance

    March 22, 2012 - VMware vCenter Configuration Manager was selected the winner in the Monitoring, Management & Performance category of the VirtualizationAdmin.com Readers' Choice Awards. SolarWinds Virtualization Manager and Quest vFoglight were runner-up and second runner-up respectively.

    vCenter Configuration Manager

    Results
    1st VMware vCenter Configuration Manager 36%
    2nd SolarWinds Virtualization Manager 15%
    3rd Quest vFoglight 11%
    4th eG VM Monitor 9%
    4th AppManager Suite 9%
    5th ManageIQ Enterprise Virtualization Management Suite 8%
    6th XTS Introspect 3%
    Others 9%
    “Our Readers’ Choice Awards give visitors to our site the opportunity to vote for the products they view as the very best in their respective category,” said Sean Buttigieg, VirtualizationAdmin.com manager. "VirtualizationAdmin.com users are specialists in their field who encounter various solutions for virtualization at the workplace. The award serves as a mark of excellence, providing the ultimate recognition from peers within the industry."
    VirtualizationAdmin.com conducts bi-monthly polls to discover which product is preferred by administrators in a particular category of third party solutions for virtualization environments. The awards draw a huge response per category and are based entirely on the visitors' votes. VirtualizationAdmin.com users can submit their votes for the current Readers' Award poll in the site's left-hand bar.

    “Our Readers’ Choice Awards give visitors to our site the opportunity to vote for the products they view as the very best in their respective category,” said Sean Buttigieg, VirtualizationAdmin.com manager. "VirtualizationAdmin.com users are specialists in their field who encounter various solutions for virtualization at the workplace. The award serves as a mark of excellence, providing the ultimate recognition from peers within the industry."
    VirtualizationAdmin.com conducts bi-monthly polls to discover which product is preferred by administrators in a particular category of third party solutions for virtualization environments. The awards draw a huge response per category and are based entirely on the visitors' votes. VirtualizationAdmin.com users can submit their votes for the current Readers' Award poll in the site's left-hand bar.
    Posted by at No comments:

    Thursday, January 12, 2012

    How to block users from accessing your site based on their IP address

    Web Hosting Articles » A simple guide to .htaccess » How to block users from accessing your site based on their IP address

    Blocking users by IP address is pretty simple with .htaccess.
    So here it is the example:

    Order allow, deny
Deny from 192.168.0.10
Deny from 212.155.
Deny from 1.2.3.4  5.6.7.8 127.0.0.1
Allow from all
     
    Let’s take a look at the code line by line:
    The first line “Order allow, deny” tells the web server the “Order”  in which the Allow and Deny directive will be evaluated. It simply says: Give access to all hosts that are not present in the Deny from list and are present in the Allow from list.  With allow, deny order Allow list is looked up first and then the web server checks the deny from list. So as we have allow from all – all access is allowed. Then the allowed access is filtered based on the Deny lists. With allow,deny access is disabled by default.
    If we change the order to “deny, allow” then all access is enabled by default and only users in the deny lists are blocked. However as the deny is being processed first allow directives will override any maching settings set in deny directives.
    The default Apache order is deny,allow. So you can skip the first line in your .htaccess file if you do not need to change the order in which the Deny and Allow rules are being evaluated by the web server.

    So to keep the .htaccess simple you can just use:

    Deny from 192.168.0.10
Deny from 212.155.
     
    Basically you can use such rules in your .htaccess file to block a particular user, or a network from accessing your site.
You can put several IP address in a Deny or Allow rule. For example:
     
    Deny from 1.2.3.4   5.6.7.9
     
    The IP addresses must be separated by a space or tab.
    You can put entire networks as


    Deny from 212.155.
     
    This will block all users which IP addresses start with 212.155
    Or to block all access to your site:


    Deny from all
     
    And then add another line to enable access only for yourself:

    Allow from 1.2.3.4

    Where “1.2.3.4” should be replaced with your computer IP address.
     


     




    Posted by at No comments:

    Wednesday, January 4, 2012

    Windows Server 2008 Tips








    Posted by at No comments:

    How to install Java ME application in mobile phone

    Overview

    Installing J2ME applications to the phones can be done in a number of ways:
    First you have to transfer the application to your mobile. You can transfer your application to the mobile from PC by making use of data cable, infrared or Bluetooth. You can install the MIDlets either with or without PC Suite or Ovi Suite.
    On Series 40 phones the application gets installed automatically. On S60 phones you need to open message (in the inbox) containing the application and install it manually. However if you use PC Suite to install the MIDlet, the installation process is started automatically on the S60 phones, although you need to step through it manually.
    Another way to transfer the MIDlet to the phone is store it (JAR and or JAD file) on a Web server and download the files using the browser of the phone (so called OTA download). Note that the server has to have the MIME types correctly defined:

    There are four ways to deploy the application into a mobile device

    Over-the-Air (OTA)

    With OTA deployment, the MIDlet (Java ME application) is installed on a Web server and then downloaded to a device via the device's Internet microbrowser. A JAR file and a JAD file are required for OTA installation. The process begins by browsing to a page that includes a link to a MIDlet suite. The link is then clicked, which causes the Web server to deliver the JAD file for the MIDlet suite to the browser. On receipt of the JAD file, it is opened and its contents are displayed. The JAD file contains a description of the MIDlet suite, including its size, version number, and who provided it. A request is then sent for the JAR file and, finally, the Web server delivers the JAR file. Once the JAR file has been delivered to the device, the suite is installed and individual MIDlets can be selected and run.

    Infrared and Bluetooth

    IR or Bluetooth technology can be used to send the MIDlet from a PC to another device .And these two technologies can also be used to send JAR files between two devices.Of course,the file must be saved in source device memory by any way before sent.And the destination device must support installing applications via MMS.

    Installing over a serial cable

    If the device has a serial cable port and connectivity software (either Nokia PC suite or the Ovi Suite) for a PC, the MIDlet can be installed on the device over a serial cable. To install the MIDlet, double-click on either the *.jar or *.jad file and follow on-screen instructions. On a PC, if jar/jad files are not associated with PC suite or Ovi suite by default, you can right click and select "open with" then choose "Ovi suite" or "PC suite" as applicable. Many devices can also be operated by connectivity software via IR or Bluetooth.

    WAP Push

    We can send as a WAP Push messages, the download link will be send to the targeted mobile number. User can download the application by clicking the link.
    WAP Push messages are specially formatted SMS messages that display an alert message to the user, and give the user the option of connecting directly to a particular URL via the mobile phone’s WAP browser
    Posted by at No comments:
    Subscribe to: Comments (Atom)

    Search