What is Logo j-Platform?
j-Platform is Logo's web-based ERP product, developed with HTML5 and Java technology. Its modules cover finance, purchasing, budgeting, projects, human resources, sales, distribution, production, and foreign trade. According to Logo, the budget module works with the other modules in both directions and goes down to appropriation tracking. Alongside the project module there is a separate Project Portal for fast data entry from the field.
On the user side, Logo highlights a role-based, personalizable desktop, in-product search, and an app-in-app approach. Authorization goes from transactions and options down to individual fields on a form.
Customization uses Logo's easy customization tools and a development environment called Logo Platform Tailor (LPT). According to Logo, the product can be installed on your own server, in a rented private environment, or in Logo's hosting, and the license can be pay-as-you-go or perpetual.
Because the product is used from a browser, no client has to be installed on dealer and branch computers. Logo positions the product as Logo Edge J-Series in its new structure, and j-Platform still has its own product page. We describe the infrastructure side of the Logo products together on our Logo ERP infrastructure page.
Companies that use j-Platform
Logo says it designed j-Platform for mid-size and large businesses. The product description highlights three profiles: businesses managing a wide dealer and branch network from one platform, construction and project companies, and holding companies that manage differently structured companies together.
In construction and project companies, site and project teams also connect to the same address from outside the company. Groups that work in several currencies and languages belong to the same audience. What these users have in common is that many of the people connecting do not work at the head office.
Three-tier web architecture
j-Platform has three tiers: the user's browser, a Java application server, and a database server. Nothing is installed in the browser. Logo's technical documents describe the product as platform independent in terms of operating system and database. The engines and versions supported in production are listed in a separate system requirements document, and they are confirmed before setup.
The Java application server runs with its own memory setting. If that setting is not matched to the number of users, the system slows down as users increase, and the service may restart. In a large installation, the application and the database run on separate servers, and their processors and memory are sized separately.
According to Logo, e-Invoice, e-Ledger, e-Archive Invoice, e-Dispatch, e-Producer Receipt, and e-Self-Employed Receipt processes are managed from within the product. It also works with the e-Reconciliation, Logo e-Collection, and Online Account Statement services, and Logo's developer documents describe a REST interface. Each of these is a connection going out of or coming into the application server, and each is defined separately on the firewall. Before setup we therefore ask which services will be used, and the inbound and outbound rules are drawn up accordingly.
j-Platform setup on ARGE Cloud
In the VPC, the Java application server and the database server run separately, and the application server connects to the database. Both run in your dedicated VPC on ARGE Cloud, our own infrastructure in a data center in Istanbul, with a highly available (HA) firewall in front of the VPC. The memory given to the Java server is set for the number of users and reviewed as that number changes. The data held by the human resources module stays in Türkiye on this system, which matters under KVKK, Türkiye's Personal Data Protection Law (Law No. 6698).
Dealers and users outside the office authenticate with SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA and can access only the j-Platform address. If the application has to be published to the internet, its traffic passes through a web application firewall (WAF). Branches connect over IPsec, MPLS, or SD-WAN, and we recommend a second link for each site.
A test environment opened from a copy of production, for LPT customizations and version upgrades, is optional, and its scope is written into the quote. Where this environment is set up, LPT customizations, new integrations, and version upgrades are tested there first. A backup is taken before an upgrade. Your Logo partner performs the upgrade and the customization, and we prepare the environment.
The database, the application configuration, and the customization files are stored in the isolated backup zone, and restore tests are performed; their frequency is written into the contract. The backup arrangement is described under our backup and disaster recovery service. Monitoring includes the memory of the Java application server, the disks, the database service, the links, and the result of the backup. Next to the VPC there is a service zone running SIEM and SOAR as well as antivirus and XDR/EDR, and the contract sets out monitoring hours and what response covers.
An application HA cluster, a database HA cluster, and a disaster recovery (DR) site in a second data center are optional. We confirm with Logo how the product behaves in a cluster and at a DR site.
Developing customizations with LPT and performing the version upgrade itself rest with your Logo partner. The license also rests with the vendor or your partner; we build and operate the infrastructure.
What we confirm with Logo before setup
- Database and versions supported for production
- Supported Java and application server versions
- Supported operating system versions
- Recommended memory and processor for the number of users
- Effect on the infrastructure if you plan to move to Logo Edge J-Series
Technologies: Java application server · Windows Server or Linux · WAF · SSL VPN · ARGE ZTNA · ARGE Cloud
Frequently asked questions
How do our dealers connect to j-Platform?
They connect from a browser. Dealer users authenticate with ARGE ZTNA and can access only the j-Platform address. If the address is to be published to the internet, a WAF is placed in front of it. Which path to choose is decided in the discovery meeting.
What happens to our j-Platform customizations during a version upgrade?
Customizations built with LPT are tested separately during an upgrade, and the customization itself is your partner's work. We take a backup before the upgrade and, optionally, open a test environment from a copy of production.
Does j-Platform run on a Linux server?
Logo's technical documents describe the product as platform independent in terms of operating system. We confirm the operating system, Java, and database versions supported in production from Logo's system requirements document.
Does the infrastructure change if we move to Logo Edge J-Series?
Logo positions the product as Logo Edge J-Series in its new structure. The scope and timing of a move rest with your Logo partner. We confirm the effect on the infrastructure with Logo before setup.
ARGE ICT provides and operates the infrastructure that Logo j-Platform runs on. Logo Yazılım is the vendor of this software and the owner of its name and trademark; ARGE ICT is not an official partner or reseller of that company. You get licensing, implementation, and functional support from the vendor or your partner.