Client JRE Requirement for Portal 9.0.2.6

I would like to know what the minimum Java Runtime Environment requirement on the client machine is for using Oracle 9iAS Portal 9.0.2.6 and 9.0.4 (10g). I have searched on OTN but to no avail. Does Oracle recommend the Microsoft JVM or the Sun JVM (e.g., Java 1.4.1._02)?
Thanks,
Kendra

Here you find certification information on the Oracle Application Server.
Peter

Similar Messages

  • What is size of jre required for oracle on redhat 7.1

    what is the file size of jre required for oracle on linux redhat .is this copy in floppy ?

    what is the file size of jre required for oracle on linux redhat .is this copy in floppy ?

  • What is the exact version of JRE required for Discoverer 10.1.2.2?

    Hello,
    I understand that through Application Server Control it is possible to set whether Discoverer Plus should use "Oracle JInitiator" or "Sun Java Plug-in 1.4".
    The problem I have is that, due to immoveable restrictions in place on the workstations where Discoverer Plus the will be used, it is not possible for the browser to automatically download and install either the Sun Java Plug-In 1.4 or JInitiator to the end-user's workstation the first time the user tries to access Discoverer Plus.
    In this environment, the only way to get either JInitiator or Sun Java Plug-in 1.4 (which I assume just means the Sun JRE) onto the users' workstations is for an administrator to manually install it. So my questions are:
    1) What is the exact version of JInitiator required to run Discoverer Plus 10.1.2.2?
    2) What is the exact version of Sun JRE required to run Discoverer Plus 10.1.2.2?
    3) If the workstations already have another more recent version of Sun JRE installed, is there any way to get Discoverer Plus to use that version?
    Thanks for your help,
    Andy

    Resolved.
    For reference, see Metalink article 465234.1

  • Client System Requirement for ADF

    Customer want to know the requirement for client machine to visit ADF application, such as cpu, memory, browse version, operation system.
    ADF's application developed by Jedevloper version 11.1.1.3

    It's just the browser.
    Read this doc http://www.oracle.com/technetwork/developer-tools/jdev/index-091111.html#Browsers for more information.
    Timo

  • What are the Client machine requirements for running Forms 6i?

    What are the minimum/ideal hardware requirements of the client machines which run forms 6i in separate frames.
    The reason for asking this is that the users have multiple sessions of separate Forms frames. When they do a lot of activity/transactions, and try to do a windows Print Screen on a MSWord file, nothing seems to print on the Word document. If they save the document and reboot the computer and open the same word document again then the screen print shows up. I am thinking it is because the separate frames take up lot of RAM. Typical configurations of our m/c are PII 400's with 64MB RAM.
    Thanks in advance.

    Hi Lionel,
    As a general rule of thumb, the ATI Rage 128 Pro will not support a 20" LCD. That being said, there are reports of it doing just that (possibly the edition that went into the cube).
    I'm not that familiar with the ins and outs of the Cube, so I can't give you authoritative information on it.
    A good place to start looking for answers is:
    http://cubeowner.com/kbase_2/
    Cheers!
    Karl

  • JAR files required for Portal Application

    Hi Experts
    I am currently migrating my custom Masthead application from NW 7.0 to NW 7.3. However, when I migrated the PAR into EAR using migration tool from Portal and imported this EAR file into NWDS7.3, the JSP pages in it shows error. Also when this EAR is directly deployed on the NW 7.3 system, it gives Portal Runtime exception.
    <%@ page import = "com.sapportals.portal.prt.session.IUserContext" %>
    <%@ page import = "com.sapportals.portal.prt.component.*" %>
    <%@ page import = "com.sapportals.portal.prt.service.laf.*" %>
    <%@ page import = "com.sap.security.api.*" %>
    <%@ page import = "com.sapportals.portal.prt.service.license.ILicenseService"%>
    <%@ page import = "com.sapportals.admin.wizardframework.util.ILocaleListService"%>
    <%@ page import = "com.sapportals.portal.navigation.*" %>
    <%@ page import = "com.sapportals.portal.prt.runtime.PortalRuntime" %>
    <%@ page import = "com.sapportals.portal.prt.util.StringUtils" %>
    <%@ taglib uri="prt:taglib:tlframework" prefix="frm" %>
    The errors shown in the JSP page are due to missing JARs. But I am having trouble in locating the required JAR files on the server. Can anybody tell about which all JARs are required and where i can find them??
    Also the imported Framework library is not accessible in the application thus there is error "Can not find the tag library descriptor for "prt:taglib:tlframework"".
    Can anybody tell me what i am missing here??
    Regards,
    Deepak

    Hi Deepak,
    Can you tell me which JAR files you added to resolve build time errors.
    I am facing the following errors after importing Std masthead from portal7.3.
    Can not find the tag library descriptor for "prt:taglib:tlframework"
    Can not find the tag library descriptor for "prt:taglib:tlhtmlb"
    componentRequest cannot be resolved
    ILocalesListService cannot be resolved
    ILocalesListService cannot be resolved to a type
    noBtn cannot be resolved
    Syntax error on token "}", delete this token
    Syntax error, insert "}" to complete Statement
    The import com.sap.portal.core cannot be resolved
    The method enableCloseAll() is undefined for the type NavigationEventsHelperService
    The method getDynamic(String, null) is undefined for the type IUMParameters
    The method getDynamic(String, String) is undefined for the type IUMParameters
    yesBtn cannot be resolved
    Please give your mail Id if possible.
    Regards,
    Sumangala

  • Requirements for Portal

    For the first time I am designing database for a portal. My Manager insisted on a document which enlists all the requirements or concerns that are to be looked while having a database for a portal. Can some one please help me find the things that are to be looked upon for designing a database for a portal

    Shiv,
    WebLogic Portal is largely CPU bound, so my recommendation is to throw as much CPU as you can (measured by total clock-speed, GHz) at it.
    We have tested with Linux and Windows and the performance does not differ that much between the platforms. JRockit is the preferred JVM due to the many optimizations which will make things faster. Solaris should only be used if you have the latest processors (not the old sparc ones) in use.
    I urge you to review the Capacity Planning Guide as a reference to see how well the WebLogic Portal Framework performs. It can be found here: http://e-docs.bea.com/wlp/docs81/capacityplanning/index.html
    Matt
    WLP Performance

  • Hardware requirements for portal performance

    I will be using BEA portal 8.1.5 to host a portal application. We are anticipating about 1 million hits per day. I am looking for some recommendations for hardware requirements to handle the load.
    - What kind of hardware (e.g. optron 220/440) and platform (Solaris or Linux) is best suited for WLP?
    and minimum of how many portal servers are recommended to keep every request under 1 second?
    Thanks
    -Shiv

    Shiv,
    WebLogic Portal is largely CPU bound, so my recommendation is to throw as much CPU as you can (measured by total clock-speed, GHz) at it.
    We have tested with Linux and Windows and the performance does not differ that much between the platforms. JRockit is the preferred JVM due to the many optimizations which will make things faster. Solaris should only be used if you have the latest processors (not the old sparc ones) in use.
    I urge you to review the Capacity Planning Guide as a reference to see how well the WebLogic Portal Framework performs. It can be found here: http://e-docs.bea.com/wlp/docs81/capacityplanning/index.html
    Matt
    WLP Performance

  • NWDI requirement for Portal 7.3

    We are upgrading from Portal 7.0 landscape to Portal 7.3 landscape. Would we be requiring a different NWDI or the existing NWDI  running in portal 7.0 landscape would work?
    Thanks,
    Appachi

    Assuming that the 7.0 NWDI is not on your portal, the 7.0 (SP 14 and up ) NWDI supports content from any NetWeaver version (6.40, 7.0x, 7.1x, 7.2, 7.3). You should create a 7.3 track  (look at the [replicate|http://help.sap.com/saphelp_nw70/helpdata/en/46/5d032c1e661cbee10000000a11466f/frameset.htm] option, which can be used to replicate tracks in the same NWDI) and "retire" the old 7.0 track once you know everything is working 100%.
    This blogs explains the above
    /people/marion.schlotte/blog/2005/10/25/jdi-software-vs-jdi-content
    Here is  a guide on using NWDI 7.0 with newer versions of NetWeaver
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f
    The 7.3 plugins you will need
    https://service.sap.com/sap/support/notes/1457908

  • Redundancy requirements for portal

    Guys,
    I need to know what kind of hardware/software is available to have a redundant portal installation to achieve high availability and load balanced enviornment.
    Can anybody give me details about load balancers available which can be used with sun portal env.
    TIA,
    Deepak.

    Deepak,
    The main requierement for a load balancer is that it must be "sticky". That is it should load-balance only the first request for a given session. There are many load balancers that can do this both software and hardware. We have used evrything from the load balancer plugin of the Web Server to the Nauticus virtual swicthes.
    For complete high availability though you need more than load balancing. You will also need to run all the underlying components in HA mode. In particular, you will need to run the Directory Server (DS), Access Manager (AM), and the web container (WS or AS) in HA configurations.
    For DS you need a Multi-Master setup and possibly some replicas to colocate with AM. For AM HA mode you will use a Message Quueue and the web containers all support HA for the HttpSession store.
    If you are thinking this should all be coalesed into a single document, we share your thoughts and we are working on it. :-)
    Here are some links to get you started.
    Directory Server:
    http://docs.sun.com/source/817-7607/rep.html#wp997029
    Access Manager:
    http://docs.sun.com/app/docs/doc/819-2136/6n4eq7si6?a=view
    Web Server:
    http://docs.sun.com/app/docs/doc/819-2629/6n4tgd1s6?a=view
    Application Server:
    http://docs.sun.com/app/docs/doc/819-4742/abejo?a=view
    HTH,
    Alex

  • How to enable Client Cert Required, only for certain URL's in the webserver

    WE are using netegrity siteminder for authentication and their plugin is executed as AuthTrans function. If I enable clientauth in server.xml ( which is basically turning on the client cert required for entire site), everything works fine. But If I want to turn that on only for certain URL's how do I do that.
    I tried turning global clientauth off in server.xml and tried using PathCehck fn"get-client-cert" in obj.conf for the URL's that need client cert, but the problem is AuthTrans is getting executed first and my netegrity plugin is throwing an error saying it cann't find the cert.
    What are diffrent options to enable cert required only for certian URL's.
    Thanks

    What is the condition you want to match?
    You can use get-client-cert in If tags in Web Server 7.0 :
    For e.g. If the condition is matched, This gets a cert, requesting it if it is not already present and failing the request if it can't obtain an acceptable cert only on POST requests.
    <If $url ~="*abc*>
    PathCheck fn="get-client-cert" method="POST" dorequest="1" require="1"
    </If>
    or
    <Object ppath="*abc*">
    PathCheck fn="get-client-cert" dorequest="1" require="1"
    <Object>
    for more details :
    http://docs.sun.com/app/docs/doc/819-2630/6n4thbiek?a=view#indexterm-380

  • Help, need to change IP address on host database for Portal

    Hi folks,
    Rather urgent assistance (as usual) needed. I have an installation working correctly on a pair of Win2k machines, one as the 9i database, one as the 9iAS/Portal. The app server has 2 NIC cards, one with public IP address (which is ok), one on the LAN. I need to reconfigure the LAN addresses on both the machines. Initial Portal install done without DNS, i.e. actual server/host addresses entered in the configuration.
    I have tried changing all of the TNS/Listner settings and the NIC card IP addresses and restarting the machines. The likes of SQLPlus work ok, with the TNS connect name allowing over the LAN access into the database with the new LAN addresses. I cannot seem to get the 9iAS/Portal to find the repository with the new addresses.
    Can someone help please? I can't find the answer in any documentation or other postings.
    Thanks in advance
    Rob

    There are other modes of operation for the plasst as well. I am listing them below but the formatting will make it difficult to read. If you like I can email it to you.
    Bill G...
    Configuring Portal when the HTTP server host name of the Infrastructure is changed
    Run the following from the $ORACLE_HOME/assistants/opca dir
    ptlasst.bat -mode SSOPARTNERCONFIG -i typical -sdad portal -host myApache.domain.com -port 7777 -silent -verbose
    NOTE:
    (1) This command would create a new Portal partner application in the SSO to reflect the changes of the Infrastructure. Before running this command please ensure to configure the SSO with the correct hostname by running the ssocfg.bat script located in the Infrastructure install (<infra_home>\sso\bin).
    The value for -host parameter will be the IP address of the infrastructure server and -port will be the port where the infrastructure http server is running on.
    Configuring Portal when the HTTP server host name of the Middle tier is changed
    ptlasst.bat -mode MIDTIER -i typical -host myApache.domain.com -port 7777 -ldap_h myOID.domain.com -ldap_p 389 -ldap_w welcome -pwd secret123 -portal_only -oh /home/oracle -chost myHostname.domain.com -cport_i 8001 -cport_a 8000 -wc_i_pwd invalidator -mc false -mi true -silent -verbose
    NOTE :
    (1) The -host value should match the serverName value of the httpd.conf
    (2) The -chost should be updated with the correct webcache hostname. In a default iAS midtier install the -host is same as the -chost.
    The value for -host parameter will be the IP address of the midtier(portal) server and -port will be the port where the portal is running on.
    Parameter Description Default Value Mandatory
    -i install_type Installation Type
    In the typical mode, the OPCA would get the Infrastructure information like the Portal schema name, Portal schema password, connect string to the Portal repository, SSO Partner application schema and password, SSO Password store schema and password and connect string to the SSO repository from the Repository Access API's.
    In the custom mode, the OPCA would take whatever is passed as the command line arguments.
    CUSTOM
    -mode mode The different install modes are : PORTAL, SSO, SSOPARTNERCONFIG, LANGUAGE, MIDTIER, ALL, SYSOBJECTS , DEINSTALL
    -s portal_schema Oracle Database schema for Portal database objects. In an iAS 9.0.2 install
    the default Portal schema name is portal portal
    -sp portal_password Password for Portal schema. In an iAS 9.0.2 install the portal schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for details. <portal_schema>
    -c portal_connect Connect string to connect to the Portal repository <hostname>:<port>:<sid>
    -p sys_password The Oracle Database password for the Oracle SYS user MANDATORY
    -sdad portal_dad DAD for the Portal schema. Create the DAD to the Portal repository through the OEM. Refer to the note "How to create and manage the Portal and SSO DAD ?" for details. <portal_schema>
    -host portal_host Hostname of the HTTP server for Portal. This should match byte to byte with whatever is present in the ServerName attribute in the $OH/Apache/Apache/conf/httpd.conf file of the midtier. MANDATORY
    -port portal_port Port of the HTTP server for Portal. The Port attribute in the $OH/Apache/Apache/conf/httpd.conf file of the midtier would provide the value. 7777
    -ldap_h oid_host_name Host name of the OID server MANDATORY
    -ldap_p oid_port_number Port number of the OID server 389
    -ldap_d oid_admin_DN Admininstration DN cn=orcladmin
    -ldap_w oid_admin_pw Password for DN welcome
    -pwd initial_password Initial Password for seeded OID users. In iAS 9.0.2 install this is defaulted to the iAS instance password of the midtier installation. MANDATORY (for ALL or MIDTIER)
    -das_public Add Portal Groups to DAS Public Groups. The values could be Y or N. The default is Y. The setting publishes the Portal groups that the user can add to when creating the new user in OID. Y
    -u default_tablespace Install Portal objects in this tablespace. The default tablespace selected should have atleast 75 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The default tablespace selected by default is users tablespace. users
    -t temporary_tablespace Use this tablespace for temporary objects. The temporary tablespace selected should have atleast 20 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The temporary tablespace selected by default is temp tablespace. temp
    -d document_tablespace Install Portal document table in this tablespace. The document tablespace selected should have atleast 4 MB of free available space and should have autoextend on. Refer to the note
    "What are the recommended tablespace size required for Portal installation ?" for details. The documented tablespace selected by default is users tablespace. <default_tablespace>
    -l logging_tablespace Install Portal logging tables in this tablespace. The Logging tablespace selected should have atleast 4 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The Logging tablespace selected by default is users tablespace. <default_tablespace>
    -in index_tablespace Install Portal index in this tablespace. The Index tablespace selected should have atleast 20 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The Index tablespace selected by default is users tablespace. <default_tablespace>
    -lang language Abbreviation for the language to install us
    -m language_mode Specifies the mode for language installation
    if sso, translations only for Login server.
    if portal, translations only for Portal.
    if -m not specified, translations are installed for Both
    -demo Install Portal webview demos
    -silent Run mode for Portal Configuration Assistant. There is no UI provided by OPCA in the iAS 9.0.2 install. Use -silent option always
    -verbose Log mode for Portal Configuration Assistant. If this parameter is not set, logging information would be in brief and the OPCA would abort the install if it encounters any errors of kind
    ORA-, PLS- or SP2 errors.
    -report Install reports integration with Portal
    -owa Install OWA packages along with Portal This option behaves the same as the SYSOBJECTS mode.
    -sso_only Configure only SSO in mid-tier mode
    -portal_only Configure only Portal in mid-tier mode
    -available Language will be available for user translation
    -chost cache_host Cache host for Web Cache <hostname>
    -cport_i cache_inv_port Cahe port for Web Cache Invalidation 1100
    -cport_a cache_adm_port Cahe port for Web Cache Administration 1000
    -wc_i_pwd wc_inv_passwd Web Cache invalidator password invalidator
    -wc wc_on_off_flag Web Cache ON/OFF flag to enable or disable WC. The default is ON. If set to OFF Portal would not use Webcache though Web Cache may be up and running. on
    -o sso_schema Oracle Database schema for Login Server objects. In an iAS 9.0.2 install the default SSO schema name is orasso orasso
    -op sso_password Password for Login Server Schema. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso. MANDATORY for the following modes:
    -MIDTIER: except when '-portal_only' is specified
    -LANGUAGE: except when '-m portal' is specified
    -DEINSTALL: except when '-drop PORTAL' is specified
    -odad sso_dad DAD for Login Server objects. Create the DAD to the SSO repository through the OEM. Refer to the note "How to create and manage the Portal and SSO DAD ?" for details. <sso_schema>
    -sso_c sso_connect Connect string to connect to the SSO repository If the Portal and SSO use the same database this option need not be passed and would default to the -c argument. <hostname>:<port>:<sid>
    -sso_h sso_host Hostname of the HTTP server for the SSO. If Portal and SSO use the same HTTP server this option need not be passed. It would default the HTTP server used for the Portal.
    -sso_p sso_port Port of the HTTP server for the SSO. If Portal and SSO use the same HTTP server this option need not be passed. It would default the HTTP port used for the Portal.
    -pa papp_schema SSO Partner Application Registration Schema. In an iAS 9.0.2 install the default Password store schema name is orasso_pa <sso_schema>_PA  
    -pap papp_password SSO PA Schema Password. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso_pa <papp_schema>
    -ps pstore_schema Password Store Schema. In an iAS 9.0.2 install the default Password store schema name is orasso_ps <sso_schema>_PS  
    -pp pstore_password Password Store Password. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso_ps. <ptore_schema>
    -pd pstore_dblink Database link from Portal schema to Password store. If the Portal and SSO use the same database this option need not be passed. <portal_schema>_DBLINK  
    -p_tns pstore_tns TNS connect string to Password Store. If the Portal and SSO use the same database this option need not be passed. The tnsalias should be created in the iAS 9.0.2 Portal middle tier.
    -s_tns portal_tns TNS connect string to Portal
    -ssotype ssotype SSO install type. Valid values are repository, midtier, all Repository
    -ultrasearch Ultrasearch configuration
    -drop drop_obj Drops either PORTAL or SSO or ALL (Both)
    if PORTAL, drops Portal schema and OID entries.
    if SSO,drops Portal schema and OID entries.
    if ALL, drops Portal and SSO schema and OID entries
    -oh oracle_home Oracle Home
    -mi midtier_install Midtier Installation
    -mc midtier_config Midtier Configuration
    -ssl Use SSL protocol for configuration. Pass this parameter only if SSL configuration is required. If this parameter is passed the -port passed should also be the SSL port of the HTTP server. Bt default this is not passed.
    -emhost em_host Enterprise Manager host for monitoring <hostname>
    -emport em_port Enterprise Manager port for monitoring 1810
    -iasname ias_name Name of the iAS instance that the install is installing on

  • Java runtime requirements for clients of Reader Extended forms

    I need to know if there is a minimum Java (JRE) requirement on the client machines to properly interact with a Reader Extended form created with Adobe LiveCycle Designer 9?
    Thank you,

    Thank you Paul and Steve for your quick responses.  I was concerned that the JRE might have been an issue causing some odd behaviors within the form at a certain client.  I guess that I will now have to pursue a different path.

  • Pre-requisites required for the local configuration of the Weblogic portal

    Hi All,
    I have got the code from the client. It is appenntly came to know that Code has been developed in Weblogic workshop.
    When we build teh application we are getting the following web services related Errors:
    ERROR: DESCRIPTION:An unexpected exception occurred while attempting to locate the run-time information for this Web Service. Error: java.lang.NullPointerException:null
    WARNING: SUGGESTION:An unexpected error occurred. Please contact [email protected] for further assistance.
    ERROR: ERROR
    ERROR: DESCRIPTION:An unexpected exception occurred while attempting to locate the run-time information for this Web Service. Error: java.lang.NullPointerException:null
    WARNING: SUGGESTION:An unexpected error occurred. Please contact [email protected] for further assistance.
    ERROR: ERROR
    ERROR: DESCRIPTION:An unexpected exception occurred while attempting to locate the run-time information for this Web Service. Error: java.lang.NullPointerException:null
    WARNING: SUGGESTION:An unexpected error occurred. Please contact [email protected] for further assistance.
    ERROR: ERROR
    ERROR: DESCRIPTION:An unexpected exception occurred while attempting to locate the run-time information for this Web Service. Error: java.lang.NullPointerException:null
    WARNING: SUGGESTION:An unexpected error occurred. Please contact [email protected] for further assistance.
    ERROR: ERROR
    ERROR: DESCRIPTION:An unexpected exception occurred while attempting to locate the run-time information for this Web Service. Error: java.lang.NullPointerException:null
    WARNING: SUGGESTION:An unexpected error occurred. Please contact [email protected] for further assistance.
    ERROR: ERROR
    ERROR: DESCRIPTION:An unexpected exception occurred while attempting to locate the run-time information for this Web Service. Error: java.lang.NullPointerException:null
    WARNING: SUGGESTION:An unexpected error occurred. Please contact [email protected] for further assistance.
    PortaleWebApp: Created control beans for 19 controls in 12703 milliseconds
    BUILD FAILED
    ERROR: Build failed with 15 error(s).
    When we deploy in the Portal weblogic server, Application is deploying with out any errors. But it is not showing any login page when I start the PTLoginMain.portal file.
    As I am completly new to this Weblogic Portal server, Please let me know, Do i need to configure the any setting before starting the application. I mean to ask you that Pre-requisites required for the local configuration of the Weblogic portal Server.
    Any Help would be much appriciated.
    Regards & thanks,
    Nirmala Vijaay Sekhar Varre

    and your server address can be resolved or not?
    Are you accessing the server from Windows or Linux?
    - On Linux try editing the /etc/hosts file and add something like: 10.241.110.105 server1.etcetera
    - On Windows try editing the C:\WINDOWS\system32\drivers\etc\hosts file and add something like: 10.241.110.105 server1.etcetera
    When this works, contact your system administrator and ask him or her to map an ip to your hostname in DNS and DHCP
    such that the servername automatically resolves the ip-address

  • Client Hardware Requirements - Portal Usage

    Hi everyone,
    is there a guideline what is the minimal/recommended hardware requirement for a Client PC. So it is able to access SAP NetWeaver 7.0 Portal.
    Maybe more detailed than "Every Modern PC"
    Is there an official SAP statement regarding this?
    Regards
    M. Stanka

    Hi Michael...
    System Requirements :
    Operating System:
    Windows 2000 (Service Pack 3); Windows XP Professional (Service Pack 1) or Windows Server 2003
    NTFS-File systems
    Internet Explorer 5.5 or higher or Firefox 1.0 or higher
    At least 1 GB RAM, 2 GB are recommended
    Intel Pentium III/1.1 GHz or higher (or compatible)
    14 GB free hard disk space (8.6 GB for the installed software and 4,9 GB for the installer software)
    High-resolution monitor (1024x768 or higher, 256 colors)
    Sun Microsystems J2SE SDK version 1.4.2_08 or 1.4.2_09 (Sun JDK 1.5 not tested)
    Please navigate to J2SE SDK version 1.4.2_09 installation archive site if you need to install this software.
    If you have already installed SAP products on your computer, you must ensure that none of the systems are called "J2E".
    The file C:\WINNT\system32\drivers\etc\services (Windows 2000) or C:\Windows\system\32\drivers\etc\services (Windows XP) must not include an entry for the ports 3601, 3201 and 50100 to 50130. A possible entry can be excluded by using the hash symbol (#).
    If no DHCP server is available on your network (which dynamically determines the IP address) or your computer is not connected to any network, you need to install the virtual interface adapter MS Loopback Adapter.
    To use Interactive Forms based on Adobe software, you must install the necessary credential file and activate it using a unique password.
    Download the latest credential and password from SDN.
    If necessary, install the SUN J2SE SDK version 1.4.2_09.
    Thanks....

Maybe you are looking for