A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_URI::$config is deprecated
Filename: core/URI.php
Line Number: 101
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Router::$uri is deprecated
Filename: core/Router.php
Line Number: 127
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$benchmark is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$hooks is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$config is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$log is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$utf8 is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$uri is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$exceptions is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$router is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$output is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$security is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$input is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$lang is deprecated
Filename: core/Controller.php
Line Number: 82
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$db is deprecated
Filename: core/Loader.php
Line Number: 396
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_DB_mysqli_driver::$failover is deprecated
Filename: database/DB_driver.php
Line Number: 371
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: Trying to access array offset on true
Filename: libraries/Email.php
Line Number: 978
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$email is deprecated
Filename: core/Loader.php
Line Number: 1283
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 295
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 169
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 238
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 318
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 359
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 282
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 289
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 304
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 314
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 315
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 317
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 375
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 110
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 143
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$session is deprecated
Filename: core/Loader.php
Line Number: 1283
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property Blogs::$user_model is deprecated
Filename: core/Loader.php
Line Number: 358
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/User.php
Line: 7
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 8
Function: __construct
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$load is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$pgmodule is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$benchmark is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$hooks is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$config is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$log is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$utf8 is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$uri is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$exceptions is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$router is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$output is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$security is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$input is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$lang is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$db is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$email is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$session is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_Loader::$user_model is deprecated
Filename: core/Loader.php
Line Number: 931
Backtrace:
File: /home1/biognosy/skmlhometuitions.in/application/controllers/Blogs.php
Line: 234
Function: view
File: /home1/biognosy/skmlhometuitions.in/index.php
Line: 315
Function: require_once
Flat File Handling in webMethods | Post Details - SKML Home Tuitions
Before we proceed we should have basic idea about flat files what they , how they are organised and how they are parsed . So, what is a flatfile , A simple text file having data in text format(non formatted text) is called flatfile , flatfiles are used since the advent of computers in business and still they are used widely . Flatfiles use the same concept used in excel and database i.e record, fields and composites . Record :- A complete row of fields and composite is called a record. Field:- We can call it a column describing the data. Composite:- If a field is composed of many subfield , then that field is called composite , example can be address it can be made up of subfield like street,house number,pincode and etc. How many different types of flatfiles are there? Flatfiles can be broadly classified into three different types based on the type of their record parsing methods , these three types are :- 1) Delimited FlatFile 2) Fixed length FlatFile 3) Variable length FlatFile Again Flatfiles can be divided into two different types based on the type of field extractors , these are :- 1) Fixed length 2) Nth field In Fixed length extractor type each field is defined by its starting index and end index , in this case the length of the field will be consatnt for every record. In Nth field extractor the field is extracted by the position of the field , such as 0,1,2 . the position starts from 0. This is the most widely used extractor type for the flatfiles because it does not limit the size of the field as in the case of Fixed length extractor. Delimited FlatFile :- In these kind of FlatFiles , the records are separated by some kind of delimiters such as newline,pipe(|),tab etc. The field extractor can be any of the two i.e fixed length or Nth field extractor. For Example :- EmployeeId,EmployeeName,DOJ,City,Department Employee,1234,QWERTY,12-08-2013,Banaglore,GHT Employee,1235,PQRSTUV,12-08-2013,Banaglore,IMBT Employee,1239,HOWAREU,19-08-2013,Banaglore,FGTH Employee,1240,IMFINE,19-08-2013,Chennai,GCS Employee,1236,HIHELLO,12-08-2013,Banaglore,QWER Fixed Length: -In these kind of flatfiles , the length of the record is specified and it acts as the record delimiter , so after a particular size next record will begin , here also any of the two extractor types can be used. For Example :- Employee1234Rakeshaaa12-08-2013BLRGCSEmployee1235Raghavend12-08-2013BLRGCSEmployee1239Ranjanqqq19-08-2013BLRGCSEmployee1240Satishxxx19-08-2013BLRGCSEmployee1236Sudhashuw12-08-2013BLRGCS Variable length :- In these kind of flatfiles , each record is preceded by two bytes which indicate the size of the record which acts as the record delimiter, here also any of the two field extractor can be used. For example see the picture below :-
Here in the above picture you can see that the first two characters/bytes are used to denote the length of record which is acting as record delimiter.The ASCII value of the corresponding character is taken in account so in the above picture the length of first record is 32 as the ASCII value of NUL is 0 and of single space is 32 , similarly the length of second record is 37 as the ASCII value of NUL is 0 and of % is 37 . For inserting ASCII characters you can use the editor Notepad ++ , use this link http://notepad-plus-plus.org/ to get notepad ++ . In order to use the ASCII panel in notepad ++ go to Edit menu then select character panel . Now the question is how to get the flatfiles into webMethods and parse it and convert it into document type. To get flat files into webMethods you have to use either of the following :- 1. create a webMethods file polling port. 2. use the inbuilt service pub.file:getFile to get the file into webMethods. 3. If the file is present on any remote system then we have to get the files using the ftp and sftp services provided by webMethods . You can use the public service from the following folder " pub.client.ftp " 4. You can write your own custom service to get the file into webMethods . I will discuss about all these above four points in my next blog , right now let us concentrate on after we get these files , how do we parse these files what are required ? In order to parse the flat files we will be using the public service provided by webMethods which is available in the package " WmFlatFile " . The most used of them are as follows :- So, In order to parse flat files in webMethods you need to create the corresponding structure of the falt file in webMethods . So, you have to create flat file schema in webMethods. There is generally two ways to create the flat file schema in webMethods :- 1. First One is directly creating the record definition and field definition that are present in the flat file , if you are directly creating the schema then you have to be sure there is record identifier coming in our flat file, otherwise webMethods will be unable to parse the flat file . 2. Second one is via flat file dictionary , in flat file dictionary you create all the record and field definition that are being used in the flat file , then you can set this dictionary in the default record of the flat file schema . The advantage of this method is that the record identifier should nt be present in the flat file. Second it's a reusable component which can be used again and again. Now we will proceed to the parsing of the flat files in webMethods , firstly we will have a look on how flat files are parsed and converted into IS Documents. 1. pub.flatFile:convertToValues :- This service converts flatfile data into IS document , the required inputs for this service is ffData(which is of Object type , it can take anything such as String,InputStream or Byte array) and ffSchema (fully qualified path of the flat file schema that you have created). The output of this service is ffValues(IData)(It is the document that has been formed from your flat file , you can map it to your corresponding document type created for your flat file schema). isValid(String) :- gives true/false accordingly if the flat file data is able to parsed successfully or unsuccessfully. errors(IData Array) :- gets populated only when isValid is false ffIterator(Object):- It is like a cursor which points to which all data has been parsed , populated when the iterate input parameter is kept true . It is generally used when we are dealing with large flat file data.
Not sure whare to join tuition right for you?
Choose the right one for you.
Get the help of the experts and find a solution that best suits your needs.
Let`s Connect
Thunder Reviews
Good easy explanation!