Thursday, July 29, 2010

SAP GUI Installation

SAP GUI INSTALLATION

Download the file sapgui.zip and place it in the folder you created. Once the zip file has been downloaded, double click on the zip file to extract the contents. A wizard will guide you through the extraction process. Make sure you "extract all" the files and choose a location you can find easily. After extracting the files, close the wizard window and open the folder where you saved the extracted files. Double click on theSapGuiSetup.exe to begin installation.


On the "Welcome Screen" please click NEXT.

The second screen is most important. You MUST click the blue text “Select All ". This will ensure all the necessary components of the GUI will be installed. After you have selected all the components, please click NEXT.

The third screen will let you choose a location to install the SAP GUI. You can either choose a custom location or accept the default by clicking NEXT.

When the installation finishes, click DONE to exit.


Regards,
Veera,
ClimbInc,
Product Support Engineer,
http://www.climb.co.jp

CGI/PERL Configuration in Apache Webserver

APACHE WEB SERVER CGI/PERL CONFIGURATION

1. Install the ApacheWebServer from Apache Site.

Publish Post

2. Install the Perl ActiveState If you are using Windows System.

Configuring Apache WebServer

1. Running Perl Scripts in a CGI directory

Edit httpd.conf file from C:\Program Files\Apache Group\Apache\conf

Find the line

ScriptAlias /cgi-bin/ "C:/Program Files/Apache Group/Apache/cgi-bin/".

It there is a hash mark(#) before the line, remove the hash character and enable it.

2. Running CGI Scripts anyWhere in your domain

1. If you don't want to be restricted to running CGI scripts within the ScriptAlias

directory in your domain, and want CGI scripts to run anywhere in your domain,

add the following line to your "httpd.conf" file.

AddHandler cgi-script .cgi


If you want the .pl extension recognised as a CGI script as well,

simply append the extension to the list, as follows:

AddHandler cgi-script .cgi .pl


Next, search for the line that says " in the file.

It should look something like this:

Options FollowSymLinks

AllowOverride None

Add "+ExecCGI" to the options list. The line now looks like this:

Options FollowSymLinks +ExecCGI

AllowOverride None


Modifying Your CGI Script

Your Perl script will typically contain an initial line of

#!/usr/bin/perl

This tells a Unix-based kernel to look for an interpreter at the path "/usr/bin/perl"

and invoke it to interpret the instructions in the file.

For example, on my Windows box,

I have to change the first line of my Perl scripts to:

#!c:/program files/perl/bin/perl.exe

Note : This is your perl installation directory.

Run the CGI/PERL Script from the Browser


Regards,
Veera
ClimbInc,
Product Support Engineer,
http://www.climb.co.jp

Monday, July 26, 2010

JBoss Installation and Configuration


JBoss Installation and Configuration in Windows system
-----------------------------------------------------------
1. Download JBOSS distribution files from the JBOSS site.
http://sourceforge.net/projects/jboss/files/JBoss/JBoss-6.0.0.M3

2. Set an Environment variable from MyComputer. Click Properties option.
Click Environment Variables button.
Click New button.
Add a Variable JAVA_HOME in the Environment wizard. Set the Java instllation folder.

Add a JBOSS_HOME variable and set the JBOSS installation folder.
3. StartUp

To Start JBOSS

Windows: Open an MS-DOS Prompt or Command Prompt window. cd %JBOSS_HOME%\bin run [-c default|minimal|all]

Note : minimal - This configuration includes only logging, the JNDI service, and the URL deployment scanner. You would want to use this configuration for starting services that don't require J2EE or as the base for a custom configuration. default - This configuration is the default. It includes all of the J2EE services exception RMI/IIOP and clustering all - This configuration includes all JBoss services.

If JBoss starts successfully, you should see something like this:
4. Open a JBOSS, to confirm the server is running.



5. If you are going to create a WAR file, you make sure the file structure. Folder
-HTML/JSP Files -WEB-INF

-
-lib -classes -web.xml

6. Create a WAR file and deploy into JBOSS application server. It is just copy a war file to deploy fodler.
7. Confirm wheather our application is deployed or not.
8. Open a browser and type the Application URL. http://localhost:8080/ClimbTest/CSVToJPEG.html

9. If we enter System.out.println line in the Program, it will be displaying in the server console.
10. To shutdown JBOSS server

Regards,
Veera,
ClimbInc,
Product Support Engineer,
http://www.climb.co.jp

Oracle Tuning Tips for Performance

These rules are simple but easy to follow and will yield lots of benefits:

  • Do not index every column in the table - have only those indexes, which are required.

  • Distribute your data to parrallelise the IO operations among multiple disks especially for those tables which have lots of IO's.

  • Try to avoid large data retrievals, since if the data being retrieved from a table is more than 10%-20% of the total data, Oracle will most likely do the FST.

  • Never do a calculation on an indexed column (e.g., WHERE salary*5 > :myvalue).

  • Whenever possible, use the UNION statement instead of OR conditions.

  • Avoid the use of NOT IN or HAVING in the WHERE clause. Instead, use the NOT EXISTS clause.

  • Always specify numeric values in numeric form and character values in character form (e.g., WHERE emp_number = 565, WHERE emp_name = 'Jones').

  • Avoid specifying NULL in an indexed column.

  • Avoid the LIKE parameter if = will suffice. Using any Oracle function will invalidate the index, causing a full-table scan.

  • Never mix data types in Oracle queries, as it will invalidate the index. If the column is numeric, remember not to use quotes (e.g., salary = 50000). For char index columns, always use single quotes (e.g., name = 'NAME').

  • Remember that Oracle's rule-based optimizer looks at the order of table names in the FROM clause to determine the driving table. Always make sure that the last table specified in the FROM clause is the table that will return the smallest number of rows. In other words, specify multiple tables with the largest result set table specified first in the FROM clause.

  • Avoid using subqueries when a JOIN will do the job.

  • Use the Oracle "decode" function to minimize the number of times a table has to be selected.

  • To turn off an index you do not want to use (only with a cost-based optimizer), concatenate a null string to the index column name (e.g., name||') or add zero to a numeric column name (e.g., salary+0). With the rule-based optimizer, this allows you to manually choose the most selective index to service your query.

  • If your query will return more than 20 percent of the rows in the table, use a full-table scan rather than an index scan.

  • Always use table aliases when referencing columns.

  • Best regards,
    Veera,
    Product Support Engineer,
    ClimbInc,
    http://www.climb.co.jp



    DBMoto - MultiServer Synchronization

    DBMoto 7 - MultiServer Synchronization setup
    1. Start DBMoto Management Center from Start->Programs->HiT….

    2. Create a New connection from Source folder.

    3. Click Next button to continue.


    4. Type the source name and choose the Database in the list box.


    5. Specify the connection parameters for the source connection. Click Test button to confirm the connection parameters are correct.



    6. For Transactional replication, to tick the checkbox and provide the sysadmin privilege user ID and password.

    7. Select a Database tables you want to replicate. Click Next button to continue.

    8. Click Finish button.

    9. If you want to add additional tables in the source connection, Click the Select Tables… option.

    10. Select a tables what you want in the list.

    11. Choose the Targets option in the folder and click Add New Connection…

    12. Click Next button to Continue.

    13. Type the target connection name and specify the Database name. Click Next button to continue.

    14. Type the connection parameters for the target connection. Click Next button to continue.

    15. Check the option and click the Verify button. Click Next button to continue.

    16. Click OK button to upgrade DBMotoLIB.

    17. Click Install button.

    18. Click Yes button.

    19. Click Next button to continue.

    20. Select a tables what you are going to replicate. If you want to create new tables, just leave it blank. Click Next button to continue.

    21. Click Finish button.

    22. Follow the screen to create a target table.


    23. Click Next button to continue.

    24. Select a source table to be copied. Click Next button to continue.

    25. Select the target connection and define the target table name.

    Click Next button to continue.

    26. Click Next button if you don’t want to change datatype.

    27. Click Next button to continue.

    28. Click Finish button.

    29. Click Yes to add the created tables in the target table list.

    30. Similarly create another two connection and select a tables.

    31. Create Multiple Replications… option in the source connection list.

    32. Click Next button to continue.

    33. Select Synchronization in the Replication Mode. Click Next button to continue.

    34. Select the source connection and library/database/schema to be replicated. Click Next button to continue.

    35. Set the correct transaction ID to read transaction from SQLServer.

    36. Click Next button to continue.

    37. Select Connection Name and Library Name. Click Next button to continue.

    38. Set the correct journal/receiver from the iSeries Server.

    39. Click Next button to continue.

    40. Select tables to replicate and Click Next to continue.

    41. Click Next button to continue.

    42. Click Start button to continue.

    43. Click Close button.

    44. Specify the Replication Mode as Synchronization, Click Next button to continue.

    45. Specify the source connection database what you are going to replicate. Click Next button to continue.

    46. Click the read button to set the transaction ID. Click OK button in the dialog box.

    47. Specify the target connection to be replicated. Click Next button to continue.

    48. Click Read button to set the transaction ID. Click OK button.

    49. Click Next button to continue.

    50. Specify the tables to put into replication. Click Next button to continue.

    51. Click Next button to continue.

    52. Click Start button to create replications.

    53. Click Close button to continue.

    54. Create a New Multiple replication for Synchronization. Click Next button to continue.

    55. Select a Source connection to be replicated. Click Next button to continue.

    56. Click Read button to set the transaction ID. Click OK button to close the dialog box.

    57. Click Next button to continue.

    58. Select a target connection to be replicated. Click Next to continue.

    59. To set the transaction ID from Oracle redo log. Click Next button to continue.

    60. Click Next button to continue.

    61. Select tables what you want to replicate. Click Next button to continue.

    62. Click Next button to continue.

    63. Click Start button to continue.

    64. Click Close button.

    65. Create a New group for MultiServer Replication.

    66. Type the Group Name and click Next button.

    67. Select a replication to insert into a group. Click Next button to continue.


    68. Click Finish button to complete the wizard.

    69. Click Yes button.

    70. Start a DBReplicator from System tray or from menu.

    71. Confirm the replication process in the monitor.


    --------------------------------------The End-------------------------------------------

    Regards,

    Veera,

    Product Support Engineer,

    http://www.climb.co.jp

    ----------------------------------

    For More Information

    http://www.hitsw.com/products_services/dbmoto.html