About SyncEx | Company | Top 10 Reasons | Partners | News | Live Demo | Free Download | Purchase | Testimonials

xTier™ as a product does not compete with BEA WebLogic or any other application server vendors. From the beginning, xTier™ was designed to bring additional value to existing infrastructures by providing a host of unique services in cross-paradigm manner. In other words, xTier™ and J2EE are entirely complementary to each other. xTier™ is not a test automation technology and therefore it brings an indirect value for reducing allocated time (cost) to the testing phase.

Yes. Since Mainsoft-based ASP.NET portlets run locally on the WebSphere Portal JSR 168 portlet container, they have access to all WebSphere Portal portlet services such as the Credential Vault service for identity mapping, the PUMA service for user management, the Model SPI for accessing the portal navigation structure, and more...

SyncEx Trax is a powerful, easy-to-use collaboration tool to help companies track business issues and automatically manage them through the resolution. In other words, it is a portal application, which provides: Status: Up-to-the-minute project information and status to team members everywhere to foster collaboration.

After deploying the SyncEx Portlets on Sun Portal Server, you must make sure that the license file is copied at the right place (please refer the Installation and configuration guide). Once you are done with this step, all you need to do is to create channels for these portlets and put them on the desired containers to view them.

If you face any problem/error in running the SyncEx Portlets, you may refer to the log file (a log file is created for each application inside the access manager --> debug folder). You may also refer to the log files YeshError.log and YASHDebug.log. These files are created on the location, which you specify inside the setup.properties file (refer to the Installation and configuration guide for configuring the logger path). You may also contact at support@syncex.com for further queries.

No. You only need your own license for IBM WebSphere Portal. You can use WebSphere Portal Test Environment on developer workstations. In staging and production, you can deploy your ASP.NET applications as native JSR 168 compliant applications to any WebSphere Portal editions, including Enable and Extend.

SyncEx Trax can be used from a broad base of industries, including broadcasting, consulting, entertainment, financial, government, hardware, health care, manufacturing, pharmaceutical, retail, software, system integration, telecommunication and transportation with little customization. As these industries always require a system that can mange their issues and their timely resolution.

The Verity application runs as a Web-App on Weblogic. Adding the Verity vindex and vsearch jars (and all other jars) to the WEB-INF/lib directory (the directory for a webapp) corrects the problem. Add the jar files to the CLASSPATH through the command line. Background: WebLogic sets the URLStreamHandlerFactory on the URL class.

www.bea.com/products/weblogic/server/index.shtml and www.weblogic.com/docs51/admindocs/apache_bridge.html.

It is an Apache module called "mod_wl" that creates a handler that forwards requests to the BEA Weblogic application server.

First of all, there is little chance that you will be able to use the on-the-fly mode (emmarun) with a full-blown J2EE container. The reason lies in the fact that many J2EE features require specialized classloading that will happen outside of EMMA instrumenting classloader. The server might run fine, but you will likely get no coverage data. Thus, the correct procedure is to instrument your classes prior to deployment (offline mode).

SyncEx Portlets are successfully deployed and tested on Sun Java System Portal 6.x. The SyncEx team is also testing these portlets on version 7.0 of Sun Java System Portal.

Once you deploy the war file of SyncEx Portlets, all you need to do is to enter in to the access manager console with the administrator id then go to the services section and click on portal desktop inside that. Here, you will find the link: Manage Channels and Containers. You can create new channel for SyncEx Portlets from here. Yes it is possible through the edit mode of SyncEx Portlets. In the edit mode you can enter the name/IP of the collaboration server you want to connect to.

Yes, it can. Some hints are provided in the EJB example tutorial and in the WebLogic 6.1 interoperation howto.

There are two ways of configuring the SyncEx portlets. You can either specify the configuration information in properties or you can provide the same in the edit mode of portlet, which will then be used as user portlet preferences.

No. There's no dependencies of SyncEx over database servers. The databases that you can use with SyncEx are Oracle, MS SQL Server and open sources like MySQL and HSQL. If you have some other database, then contact us to receive SyncEx set for it.

Mainsoft's SharePoint Federator enables you to integrate contents stored on Windows SharePoint Services (WSS) and Microsoft Office SharePoint Servers (MOSS) into WebSphere Portal server. Use the SharePoint Federator when you want to: Mainsoft SharePoint Federator features ready-to-use portlets (available in source form) and an ASP.NET control toolkit. To demo the federation capabilities, download the SharePoint portlets and the SharePoint SDK. Yes.

You can integrate SharePoint document libraries, announcements, events, contacts, tasks, and customized SharePoint lists using the Federator. You cannot integrate SharePoint Web Parts using the Federator. However, you may use the Mainsoft, Portal Edition, to integrate Web Parts into WebSphere Portal, provided you have access to the source code.

No, the Federator portlets are pure Java portlets (JSR 168), which you can deploy via the standard WebSphere Portal administration portlets. When you use the SDK to build custom portlets or enterprise composite applications, you may want to optimize your deployment by deploying the Mainsoft Java runtime libraries into the portal server shared class-path.